All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] defer: Use \slash to permit line break behind '/'
Date: Wed, 16 Jan 2019 15:00:19 -0800	[thread overview]
Message-ID: <20190116230019.GO1215@linux.ibm.com> (raw)
In-Reply-To: <c65d597e-9191-573e-af15-1fb695b5b472@gmail.com>

On Thu, Jan 17, 2019 at 07:33:14AM +0900, Akira Yokosawa wrote:
> >From 8d305759c347fa6d1a786adfa2b0199a136d29df Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Thu, 17 Jan 2019 07:17:18 +0900
> Subject: [PATCH] defer: Use \slash to permit line break behind '/'
> 
> These captions were hyphenated in a strange way in 2c layout
> as show below:
> 
>                                   ... Ad-
>     d/Delete ...
> 
> By this change, they are broken behind the '/' character:
> 
>                                   ... Add/
>     Delete ...
> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>

That is strange, good eyes!  Queued and pushed, thank you!

							Thanx, Paul

> ---
>  defer/hazptr.tex  | 2 +-
>  defer/refcnt.tex  | 2 +-
>  defer/seqlock.tex | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/defer/hazptr.tex b/defer/hazptr.tex
> index 98ba002..fe319ea 100644
> --- a/defer/hazptr.tex
> +++ b/defer/hazptr.tex
> @@ -188,7 +188,7 @@ and in other publications~\cite{ThomasEHart2007a,McKenney:2013:SDS:2483852.24838
>  
>  \begin{listing}[tbp]
>  \input{CodeSamples/defer/route_hazptr@add_del.fcv}
> -\caption{Hazard-Pointer Pre-BSD Routing Table Add/Delete}
> +\caption{Hazard-Pointer Pre-BSD Routing Table Add\slash Delete}
>  \label{lst:defer:Hazard-Pointer Pre-BSD Routing Table Add/Delete}
>  \end{listing}
>  
> diff --git a/defer/refcnt.tex b/defer/refcnt.tex
> index 79b5f18..f385389 100644
> --- a/defer/refcnt.tex
> +++ b/defer/refcnt.tex
> @@ -13,7 +13,7 @@
>  
>  \begin{listing}[tbp]
>  \input{CodeSamples/defer/route_refcnt@add_del.fcv}
> -\caption{Reference-Counted Pre-BSD Routing Table Add/Delete (BUGGY!!!)}
> +\caption{Reference-Counted Pre-BSD Routing Table Add\slash Delete (BUGGY!!!)}
>  \label{lst:defer:Reference-Counted Pre-BSD Routing Table Add/Delete}
>  \end{listing}
>  
> diff --git a/defer/seqlock.tex b/defer/seqlock.tex
> index 3eabf31..abb9f37 100644
> --- a/defer/seqlock.tex
> +++ b/defer/seqlock.tex
> @@ -270,7 +270,7 @@ increment of the sequence number on line~\lnref{inc}, then releases the lock.
>  
>  \begin{listing}[tbp]
>  \input{CodeSamples/defer/route_seqlock@add_del.fcv}
> -\caption{Sequence-Locked Pre-BSD Routing Table Add/Delete (BUGGY!!!)}
> +\caption{Sequence-Locked Pre-BSD Routing Table Add\slash Delete (BUGGY!!!)}
>  \label{lst:defer:Sequence-Locked Pre-BSD Routing Table Add/Delete}
>  \end{listing}
>  
> -- 
> 2.7.4
> 


      reply	other threads:[~2019-01-16 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 22:33 [PATCH] defer: Use \slash to permit line break behind '/' Akira Yokosawa
2019-01-16 23:00 ` 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=20190116230019.GO1215@linux.ibm.com \
    --to=paulmck@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.