linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
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 07:33:56 -0600	[thread overview]
Message-ID: <87y218r9dn.fsf@meer.lwn.net> (raw)
In-Reply-To: <8c36fd06-b378-409b-6772-972b76cf630c@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> Hi Jon,
>
> On Wed, 16 Mar 2022 15:07:10 -0600
> Jonathan Corbet <corbet@lwn.net> wrote:
>
>> 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 interpreted Peter's response differently.  I invited him to express
his opposition to *this patch* and he didn't do that.  As we know, Peter
does not suffer from an inability to express his thoughts explicitly and
succinctly; "implied NAK" is not normally his way.

Or are you saying that I should follow his message to the letter and
back out the entire RST conversion? :)

jon

  reply	other threads:[~2022-03-17 13:34 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
2022-03-17 13:33     ` Jonathan Corbet [this message]
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=87y218r9dn.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --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 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).