Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [GIT PULL] Another round of qqz improvement
Date: Thu, 7 Jul 2016 11:52:28 -0700	[thread overview]
Message-ID: <20160707185228.GL4650@linux.vnet.ibm.com> (raw)
In-Reply-To: <38f7bfb9-8532-02fc-524c-bfe0cd9115c6@gmail.com>

On Thu, Jul 07, 2016 at 10:46:18PM +0900, Akira Yokosawa wrote:
> On 2016/07/06 19:45:57 -0700, Paul E. McKenney wrote:
> >On Thu, Jul 07, 2016 at 07:29:24AM +0900, Akira Yokosawa wrote:
> >>Hi Paul,
> >>
> >>This is another round of qqz improvement.
> >>1st and 3rd patch improve vertical spacings in Appendix D.
> >>2nd patch modifies the target of back link at the end of QQA
> >>to the end of QQ in the main text.
> >>This makes it easier to continue reading after reading an Answer.
> >>The white box at the end of QQA is added recently, and its change
> >>in behavior will cause little confusion if any, I think.
> >
> >Hello, Akira,
> >
> >I applied the first and third, but skipped the second.  I tried it, but
> >couldn't help thinking that showing the quick quiz upon return might
> >help with continuity.  "What was I doing again?  Oh, right, I just came
> >back to the quick quiz on the page."
> 
> I see. I respect your preference.
> As a matter of fact, it took a few days for me to get used to the modified
> behavior. When you expect the behavior, it would feel smoother especially
> where a Quick Quiz is broken at the bottom of a left column in two column
> format.
> 
> Anyway, I agree with you that current behavior is suitable as a default.

I do plan to do another release soon, and the release note will highlight
Paolo's and your work on this.  So let's see what the readers think!

							Thanx, Paul

> >>---
> >>The following changes since commit 22af283e2a52cdf4a1c944fc97f00ce6a7a25ef8:
> >>
> >>  Add diagnostics to route_rcu to reliably detect use-after-free (2016-07-05 15:52:16 -0700)
> >>
> >>are available in the git repository at:
> >>
> >>  https://github.com/akiyks/perfbook.git qqz-use-vspace
> >>
> >>for you to fetch changes up to 746d78491c4dc47bcf72bfaf23724d568582d192:
> >>
> >>  qqz: Give room for \parskip to suppress orphans (2016-07-07 07:07:17 +0900)
> >>
> >>----------------------------------------------------------------
> >>Akira Yokosawa (3):
> >>      qqz: Use \vspace{} for vertical spacing in Appendix D.
> >>      qqz: Modify back link target at end of QQA to end of QQ
> >>      qqz: Give room for \parskip to suppress orphans
> >>
> >> qqz.sty | 22 +++++++++++++++++-----
> >> 1 file changed, 17 insertions(+), 5 deletions(-)
> >>
> >
> >
> 


  reply	other threads:[~2016-07-07 18:52 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 [this message]
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

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=20160707185228.GL4650@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