From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 2/3] cpu/overheads: Don't break just after nn-mm
Date: Sat, 4 Nov 2017 09:09:04 -0700 [thread overview]
Message-ID: <20171104160904.GV3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <0347fa89-d3c2-c11d-f47c-737fa177dfb9@gmail.com>
On Sat, Nov 04, 2017 at 02:24:22PM +0900, Akira Yokosawa wrote:
> On 2017/11/03 21:40:25 -0700, Paul E. McKenney wrote:
> > On Sat, Nov 04, 2017 at 10:40:40AM +0900, Akira Yokosawa wrote:
> >> >From 96995ec9781970d633f554579465e9f053ec316a Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Sat, 4 Nov 2017 07:44:36 +0900
> >> Subject: [PATCH 2/3] cpu/overheads: Don't break just after nn-mm
> >>
> >> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> >
> > You lost me with this one. Shouldn't there be a non-breaking space
> > between the "350-500" and the "sheets"? Or is there some magic here
> > that I am missing?
>
> I intentionally chose normal space because the preceding number is
> 3 digits and "sheets" can't be hyphenated. It can cause large underfil
> in 2c layout.
> In the current Answer, line breaking is done at different places in
> both 1c and 2c layout, so it doesn't matter at the moment.
>
> Also, non-breaking spaces can be enforced by a script something like
> hypen2endash.sh. The added pattern in Patch #1 does the conversion
> to nbsp. (I use this script for mostly 1c layout.)
>
> Thoughts?
OK, I am finally seeing the connection between this change and the
change to the sripts. So, yes, it has no direct effect on LaTeX,
but does have an indirect effect after the scripts have run. And some
quick-quiz answers do look much better as well!
I applied and pushed all three, thank you
> Thanks, Akira
>
> >
> > Thanx, Paul
> >
> >> ---
> >> cpu/overheads.tex | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/cpu/overheads.tex b/cpu/overheads.tex
> >> index bd4c814..366b071 100644
> >> --- a/cpu/overheads.tex
> >> +++ b/cpu/overheads.tex
> >> @@ -290,8 +290,8 @@ cycles, as shown in the ``Global Comms'' row.
> >> How can I possibly get my head around them?
> >> \QuickQuizAnswer{
> >> Get a roll of toilet paper.
> >> - In the USA, each roll will normally have somewhere around 350-500
> >> - sheets.
> >> + In the USA, each roll will normally have somewhere around
> >> + 350-500 sheets.
> >> Tear off one sheet to represent a single clock cycle, setting it aside.
> >> Now unroll the rest of the roll.
> >>
> >> --
> >> 2.7.4
> >>
> >>
> >
> >
>
next prev parent reply other threads:[~2017-11-04 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 1:38 [PATCH 0/3] Fix layout hiccups in answers to quick quizzes Akira Yokosawa
2017-11-04 1:39 ` [PATCH 1/3] hyphen2endash.sh: Add patterns for 'nn-mm days' and 'nn-mm sheets' Akira Yokosawa
2017-11-04 1:40 ` [PATCH 2/3] cpu/overheads: Don't break just after nn-mm Akira Yokosawa
2017-11-04 4:40 ` Paul E. McKenney
2017-11-04 5:24 ` Akira Yokosawa
2017-11-04 16:09 ` Paul E. McKenney [this message]
2017-11-04 1:41 ` [PATCH 3/3] Fix layout hiccups in answers to quick quizzes 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=20171104160904.GV3624@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