From: Jani Nikula <jani.nikula@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Matthew Wilcox <willy@infradead.org>
Cc: John Garry <john.garry@huawei.com>,
corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] docs/completion.txt: Fix a couple of punctuation nits
Date: Thu, 11 Oct 2018 21:46:56 +0300 [thread overview]
Message-ID: <87bm80wcbj.fsf@intel.com> (raw)
In-Reply-To: <20181011154143.GB9867@hirez.programming.kicks-ass.net>
On Thu, 11 Oct 2018, Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Oct 11, 2018 at 08:29:10AM -0700, Matthew Wilcox wrote:
>> On Wed, Oct 10, 2018 at 10:56:32PM +0800, John Garry wrote:
>> > This patch fixes a couple of punctuation nits which can make the document
>> > more correct and readable.
>> >
>> > Also missing "()" are added to some function references for consistency.
>>
>> While there's nothing wrong here, any chance you want to try converting
>> it to .rst and adding it to the overall index? It looks a lot like
>> rst already.
>
> I, on principle, will not touch rst files. They are inferior to txt files.
$ git shortlog --author=Zijlstra -- Documentation/scheduler/
It does not look like you touch txt files either.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2018-10-11 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 14:56 [PATCH] docs/completion.txt: Fix a couple of punctuation nits John Garry
2018-10-10 15:47 ` Randy Dunlap
2018-10-11 8:39 ` [tip:sched/core] sched/completions/Documentation: " tip-bot for John Garry
2018-10-11 8:40 ` [tip:sched/core] sched/completions/Documentation: Clean up the document some more tip-bot for Ingo Molnar
2018-10-11 22:06 ` Ingo Molnar
2018-10-11 15:29 ` [PATCH] docs/completion.txt: Fix a couple of punctuation nits Matthew Wilcox
2018-10-11 15:41 ` Peter Zijlstra
2018-10-11 18:46 ` Jani Nikula [this message]
2018-10-12 9:32 ` Peter Zijlstra
2018-10-12 17:27 ` Jonathan Corbet
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=87bm80wcbj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=john.garry@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=willy@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 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.