All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] docparse: Unify Description and Algorithm titles
Date: Thu, 11 Mar 2021 09:38:45 +0800	[thread overview]
Message-ID: <604974A5.6080604@cn.fujitsu.com> (raw)
In-Reply-To: <20210308160122.24522-2-pvorel@suse.cz>

On 2021/3/9 0:01, Petr Vorel wrote:
> Instead owo'n'df fixing sources docs unify it during doc generation.
Hi Petr,

Your fix unifies Description and Algorithm in metadata.{html, pdf}.
I wonder if we should do the conversion in metadata.json instead.

Best Regards,
Xiao Yang
> Signed-off-by: Petr Vorel<pvorel@suse.cz>
> ---
>   docparse/testinfo.pl | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docparse/testinfo.pl b/docparse/testinfo.pl
> index b5ab02bc1..f3a657d4d 100755
> --- a/docparse/testinfo.pl
> +++ b/docparse/testinfo.pl
> @@ -308,7 +308,7 @@ sub content_all_tests
>
>   				# fix formatting for asciidoc [DOCUMENTATION] =>  *DOCUMENTATION*
>   				if ($doc =~ s/^\[(.*)\]$/$1/) {
> -					$doc = paragraph(bold($doc));
> +					$doc = paragraph(bold(ucfirst(lc($doc))));
>   				}
>
>   				$content .= "$doc\n";




  reply	other threads:[~2021-03-11  1:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 16:01 [LTP] [PATCH 1/2] docparse: Use C standard comment end Petr Vorel
2021-03-08 16:01 ` [LTP] [PATCH 2/2] docparse: Unify Description and Algorithm titles Petr Vorel
2021-03-11  1:38   ` Xiao Yang [this message]
2021-03-11  6:44     ` Petr Vorel
2021-03-12 10:42   ` Cyril Hrubis
2021-03-12 11:02     ` Petr Vorel
2021-03-12 14:52       ` Xiao Yang
2021-03-11  1:30 ` [LTP] [PATCH 1/2] docparse: Use C standard comment end Xiao Yang
2021-03-12 10:41 ` Cyril Hrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=604974A5.6080604@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.