From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Suggestion (was Re: [GIT PULL] Another round of qqz improvement)
Date: Fri, 8 Jul 2016 19:56:21 -0700 [thread overview]
Message-ID: <20160709025621.GU4650@linux.vnet.ibm.com> (raw)
In-Reply-To: <ac131a7f-76d7-39c0-8388-75db2a035a38@gmail.com>
On Sat, Jul 09, 2016 at 10:44:25AM +0900, Akira Yokosawa wrote:
> On 2016/07/08 15:18:43 -0700, Paul E. McKenney wrote:
> [snip]
> >>And how soon would the release be?
> >
> >With luck, in a few days. More likely in a few weeks.
> >
> >>I'm preparing a (hopefully) final round of cosmetic fixes.
> >>It's getting larger than I expected. I need to cleanup the commits to
> >>distinguish actual fixes of something from just cosmetic ones so that you can
> >>review them easily. It may take another week or so.
> >
> >Well, unless the weekend's writing goes faster than normal (or, equivalently,
> >as fast as hoped), you should make the current release. Otherwise, there
> >will be another release, hopefully much sooner than 18 months from now.
>
> Before I forget it, I noticed a small issue I don't plan to fix in the cosmetic
> fixes.
>
> In Section 1.1, there is no mention of Chapter 16. You might want to add
> a sentence there.
Good catch! I forgot to add the new real-time chapter. Fixed with your
Reported-by.
Thanx, Paul
prev parent reply other threads:[~2016-07-09 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:29 [GIT PULL] Another round of qqz improvement Akira Yokosawa
2016-07-07 2:45 ` Paul E. McKenney
2016-07-07 13:46 ` Akira Yokosawa
2016-07-07 18:52 ` Paul E. McKenney
2016-07-08 15:54 ` Akira Yokosawa
2016-07-08 22:18 ` Paul E. McKenney
2016-07-09 1:44 ` Suggestion (was Re: [GIT PULL] Another round of qqz improvement) Akira Yokosawa
2016-07-09 2:56 ` Paul E. McKenney [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=20160709025621.GU4650@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.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