public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor <igormtorrente@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Igor <igormtorrente@gmail.com>, linux-doc@vger.kernel.org
Subject: Re: About the .txt docs files
Date: Sun, 21 Feb 2021 15:16:49 -0300	[thread overview]
Message-ID: <YDKjkTYz3NyqW2qk@debian-vm> (raw)
In-Reply-To: <7929a6a1-65b0-a057-b351-23326981ad5d@infradead.org>

On Sat, Feb 20, 2021 at 03:07:06PM -0800, Randy Dunlap wrote:
> Hi,
> 
> Yes, it's good to ask.
> 
> On 2/20/21 2:46 PM, Igor wrote:
> > Hi everyone,
> > 
> > I was converting the memory-barrier.txt to .rst so it can be properly
> > displayed alongside the rest of the documentation that is already
> > converted to .rst.
> > 
> > After I started, I realize that is better to ask if is desirable for
> > these files to be converted in the first place.
> > 
> > So, that is my question, from the files in the following list there
> > any that would be desirable for the conversion?
> > 
> > memory-barriers.txt
> > atomic_t.txt
> > atomic_bitops.txt
> 
> For the atomic files, my understanding is that the owners don't
> want to have them converted to .rst files.
> That could easily be true of memory-barriers.txt as well.
>

Ohhh, ok then.

> 
> > admin-guide/spkguide.txt
> > filesystems/dax.txt
> > filesystems/path-lookup.txt
> 
> 
> thanks.
> -- 
> ~Randy
> 

Thanks Randy!

      reply	other threads:[~2021-02-21 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 22:46 About the .txt docs files Igor
2021-02-20 23:07 ` Randy Dunlap
2021-02-21 18:16   ` Igor [this message]

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=YDKjkTYz3NyqW2qk@debian-vm \
    --to=igormtorrente@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=rdunlap@infradead.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