public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/1] README.md: Document IRC
Date: Mon, 14 Nov 2022 14:11:04 +0000	[thread overview]
Message-ID: <87tu31sjze.fsf@suse.de> (raw)
In-Reply-To: <Y3JGoc2V7VjR0q9Z@pevik>

Hello,

Petr Vorel <pvorel@suse.cz> writes:

> Hi Richie,
>
>> Hello,
>
>> Petr Vorel <pvorel@suse.cz> writes:
>
>> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
>> > ---
>> > changes v1->v2
>> > * s/on/at/
>
>> > Kind regards,
>> > Petr
>
>> >  README.md | 3 +++
>> >  1 file changed, 3 insertions(+)
>
>> > diff --git a/README.md b/README.md
>> > index d45d1ee44..89b2640c1 100644
>> > --- a/README.md
>> > +++ b/README.md
>> > @@ -22,6 +22,9 @@ http://lists.linux.it/listinfo/ltp
>> >  LTP mailing list is archived at:
>> >  https://lore.kernel.org/ltp/
>
>> > +IRC
>> > +#ltp at https://libera.chat/[irc.libera.chat]
>
> Hi Richie,
>
>> Won't the # make it a top level heading?
> Well, that would be if there was a separate line between those two lines.
>
>> https://daringfireball.net/projects/markdown/syntax#header
>
> Thus this would work. But I put asciidoc syntax (used in our wiki),
> instead of markdown.
>
> Therefore the correct syntax for README.md is:
>
> IRC #ltp at: [https://libera.chat/](irc.libera.chat)
>
> Kind regards,
> Petr

Well, either way:

Acked-by: Richard Palethorpe <rpalethorpe@suse.com>


-- 
Thank you,
Richard.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-11-14 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 14:54 [LTP] [PATCH v2 1/1] README.md: Document IRC Petr Vorel
2022-11-14 12:05 ` Richard Palethorpe
2022-11-14 13:46   ` Petr Vorel
2022-11-14 14:11     ` Richard Palethorpe [this message]
2022-11-14 14:58       ` Petr Vorel

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=87tu31sjze.fsf@suse.de \
    --to=rpalethorpe@suse.de \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox