From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] howto: Add unbreakable space for volume number
Date: Mon, 31 Jul 2017 08:47:46 -0700 [thread overview]
Message-ID: <20170731154746.GC3730@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170731055005.18716-1-sj38.park@gmail.com>
On Mon, Jul 31, 2017 at 02:50:05PM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good catch, applied, thank you!
Thanx, Paul
> ---
> howto/howto.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/howto/howto.tex b/howto/howto.tex
> index 323f95f..90abb14 100644
> --- a/howto/howto.tex
> +++ b/howto/howto.tex
> @@ -276,10 +276,10 @@ Fortunately, there are many alternatives available to you:
> on programming-language pragmatics.
> \item If you are interested in an object-oriented patternist
> treatment of parallel programming focussing on C++,
> - you might try Volumes~2 and 4 of Schmidt's POSA
> + you might try Volumes~2 and~4 of Schmidt's POSA
> series~\cite{SchmidtStalRohnertBuschmann2000v2Textbook,
> BuschmannHenneySchmidt2007v4Textbook}.
> - Volume 4 in particular has some interesting chapters
> + Volume~4 in particular has some interesting chapters
> applying this work to a warehouse application.
> The realism of this example is attested to by
> the section entitled ``Partitioning the Big Ball of Mud'',
> --
> 2.10.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2017-07-31 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 5:50 [PATCH] howto: Add unbreakable space for volume number SeongJae Park
2017-07-31 15:47 ` 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=20170731154746.GC3730@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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