From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Joey Pabalinas <joeypabalinas@gmail.com>,
Willy Tarreau <w@1wt.eu>,
mingo@kernel.org, rdunlap@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc
Date: Tue, 1 Jan 2019 09:57:23 -0800 [thread overview]
Message-ID: <20190101175723.GX4170@linux.ibm.com> (raw)
In-Reply-To: <20190101002136.fvn3hy7ybkhmgd3r@gmail.com>
On Mon, Dec 31, 2018 at 02:21:36PM -1000, Joey Pabalinas wrote:
> On Mon, Dec 31, 2018 at 12:08:54PM -0800, Paul E. McKenney wrote:
> > On Sat, Dec 29, 2018 at 09:40:20PM -1000, Joey Pabalinas wrote:
> > > On Sun, Dec 30, 2018 at 08:08:46AM +0100, Willy Tarreau wrote:
> > > > Definitely! Same, I won't emit a patch just for this, Paul already queued it.
> > >
> > > Yeah, not that big a deal :)
> > >
> > > Reviewed-by: Joey Pabalinas <joeypabalinas@gmail.com>
> >
> > But as long as I am rebasing to add the Reviewed-by, might as well
> > update the others.
> >
> > The English rules for capitalization and lists are baroque and completely
> > unsuited to word processors ("If any list item is longer than one line,
> > capitalize all the items."), but in this case each item has multiple
> > sentences, so it makes sense to capitalize.
> >
> > Please see below for the updated commit, and thank you all!
>
> Interesting, I had no idea it was actually that odd, hah.
The horrible thing is the guy that informed me of this had English as
his third or fourth of something like seven languages. Yet he knew
English better than I ever will. Worst of all, when I would complain
about some inconsistency, his response was simply "Mr. McKenney, it is
your language, not mine!" ;-)
Thanx, Paul
next prev parent reply other threads:[~2019-01-01 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 18:02 [PATCH-v2 0/3] rcutorture: minor nolibc fixes Willy Tarreau
2018-12-29 18:02 ` [PATCH 1/4] rcutorture/nolibc: fix the clobbered registers in the MIPS syscall definition Willy Tarreau
2018-12-29 18:02 ` [PATCH 2/4] rcutorture/nolibc: fix some poor indentation and alignment Willy Tarreau
2018-12-29 22:30 ` Joey Pabalinas
2018-12-31 19:43 ` Paul E. McKenney
2018-12-29 18:02 ` [PATCH 3/4] rcutorture/nolibc: add a bit of documentation to explain how to use nolibc Willy Tarreau
2018-12-29 22:33 ` Joey Pabalinas
2018-12-30 7:08 ` Willy Tarreau
2018-12-30 7:40 ` Joey Pabalinas
2018-12-31 20:08 ` Paul E. McKenney
2018-12-31 23:56 ` Willy Tarreau
2019-01-01 0:21 ` Joey Pabalinas
2019-01-01 17:57 ` Paul E. McKenney [this message]
2018-12-29 22:35 ` Randy Dunlap
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=20190101175723.GX4170@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=joeypabalinas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rdunlap@infradead.org \
--cc=w@1wt.eu \
/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).