cti-tac.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Carlos O'Donell <carlos@redhat.com>, cti-tac@lists.linuxfoundation.org
Subject: Re: [PATCH 2/5] Add a toplevel README
Date: Thu, 7 Mar 2024 16:54:18 -0500	[thread overview]
Message-ID: <99745e58-72ec-433a-8f0b-6f3153796847@gotplt.org> (raw)
In-Reply-To: <e019481d-4977-475e-b575-2aa2f04bb483@redhat.com>

On 2024-03-07 16:06, Carlos O'Donell wrote:
> On 3/7/24 16:00, Siddhesh Poyarekar wrote:
>> On 2024-03-07 15:25, Carlos O'Donell wrote:
>>> On 3/7/24 14:30, Siddhesh Poyarekar wrote:
>>>> Add basic instructions to allow one to test and later submit changes for
>>>> review and inclusion.
>>>>
>>>> Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
>>>
>>> Content looks good though, you can keep my RB and push so long as you call it README.md.
>>>
>>> Reviewed-by: Carlos O'Donell <carlos@redhat.com>
>>
>> I'm calling it README.rst instead, since it's more rst than md.  Is that fine?
> 
> No. The README.md is intended to be rendered by forges that mirror the repo
> and should be in markdown regardless of what we use for the project itself
> (rST). For example Github only renders markdown and a README.rst would not
> be rendered there, we'd need to use pandoc to sync an update of the same
> file but converted.
> 
> Suggestion: Call it README.md; and keep it in markdown.
> 

Ack, I changed the name (and format, e.g. # for h1, `` for code blocks, 
etc.) to markdown and pushed this.

Sid

  reply	other threads:[~2024-03-07 21:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 19:30 [PATCH 0/5] Multiple website cleanups Siddhesh Poyarekar
2024-03-07 19:30 ` [PATCH 1/5] projects/glibc: slightly adjust the structure Siddhesh Poyarekar
2024-03-07 20:22   ` Carlos O'Donell
2024-03-07 20:38     ` Siddhesh Poyarekar
2024-03-07 20:45       ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 2/5] Add a toplevel README Siddhesh Poyarekar
2024-03-07 20:24   ` Carlos O'Donell
2024-03-07 20:25   ` Carlos O'Donell
2024-03-07 21:00     ` Siddhesh Poyarekar
2024-03-07 21:06       ` Carlos O'Donell
2024-03-07 21:54         ` Siddhesh Poyarekar [this message]
2024-03-07 19:30 ` [PATCH 3/5] services: Clean up links to projects Siddhesh Poyarekar
2024-03-07 20:25   ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 4/5] tac/audit: Minor cleanups Siddhesh Poyarekar
2024-03-07 20:26   ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 5/5] faq: Reformat so that it's not a list Siddhesh Poyarekar
2024-03-07 20:27   ` Carlos O'Donell

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=99745e58-72ec-433a-8f0b-6f3153796847@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=carlos@redhat.com \
    --cc=cti-tac@lists.linuxfoundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).