All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, mingo@redhat.com,
	peterz@infradead.org, siyanteng01@gmail.com,
	siyanteng@loongson.cn, tangyeechou@gmail.com,
	tangyizhou@huawei.com, zhengbin13@huawei.com
Subject: Re: [PATCH v2] docs: scheduler: Convert schedutil.txt to ReST
Date: Thu, 17 Mar 2022 10:12:30 +0900	[thread overview]
Message-ID: <8c36fd06-b378-409b-6772-972b76cf630c@gmail.com> (raw)
In-Reply-To: <871qz1txmp.fsf@meer.lwn.net>

Hi Jon,

On Wed, 16 Mar 2022 15:07:10 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> Tang Yizhou <tangyizhou@huawei.com> writes:
> 
>> All other scheduler documents have been converted to *.rst. Let's do
>> the same for schedutil.txt.
>>
>> Also fixed some typos.
>>
>> Signed-off-by: Tang Yizhou <tangyizhou@huawei.com>
>> ---
>> v2:
>> Remove unnecessary space-to-tab conversions.
>>
>>  Documentation/scheduler/index.rst             |  1 +
>>  .../{schedutil.txt => schedutil.rst}          | 30 +++++++++++--------
>>  2 files changed, 18 insertions(+), 13 deletions(-)
>>  rename Documentation/scheduler/{schedutil.txt => schedutil.rst} (92%)
> 
> I have applied this version.

Jon, I think you missed Peter'z (implied) Nak on this conversion.

Quote from Peter's message [1]:

> As I'm sure you're aware, I'd *love* to convert the whole lot to plain
> text again :-)
> 
> People, throughout the ages, have been able to read plain text, I don't
> see why it should be made more difficult than that.

I'd recommend you to drop this from docs-next for now.
I think this should go through -tip.

I don't want to see another unfortunate removal of doc.
Remember what happened to atomc_opt.txt:

  - conversion [2]
  - addition of alternative plaintext docs [3] (See final words in the changelog.)
  - removal [4]

[1]: https://lore.kernel.org/r/20220312114017.GA6235@worktop.programming.kicks-ass.net
[2]: 326bc876fed4 ("Documentation/atomic_ops.txt: convert to ReST markup")
[3]: 706eeb3e9c6f ("Documentation/locking/atomic: Add documents for new atomic_t APIs")
[4]: f0400a77ebdc ("atomic: Delete obsolete documentation")

        Thanks, Akira
 

> 
> Thanks,
> 
> jon

  reply	other threads:[~2022-03-17  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12  7:07 [PATCH v2] docs: scheduler: Convert schedutil.txt to ReST Tang Yizhou
2022-03-16 21:07 ` Jonathan Corbet
2022-03-17  1:12   ` Akira Yokosawa [this message]
2022-03-17 13:33     ` Jonathan Corbet
2022-03-17 14:07       ` Akira Yokosawa

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=8c36fd06-b378-409b-6772-972b76cf630c@gmail.com \
    --to=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    --cc=tangyeechou@gmail.com \
    --cc=tangyizhou@huawei.com \
    --cc=zhengbin13@huawei.com \
    /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.