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: [PATCH 0/6] Convert code snippets to "listing" environment
Date: Tue, 8 Aug 2017 15:33:14 -0700	[thread overview]
Message-ID: <20170808223314.GK3730@linux.vnet.ibm.com> (raw)
In-Reply-To: <acc91026-d2fe-3cc8-7c6f-f43662b533b8@gmail.com>

On Wed, Aug 09, 2017 at 07:04:42AM +0900, Akira Yokosawa wrote:
> >From 3a2394edf4c62cd0a051cf251d36702c6baa2c1a Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 9 Aug 2017 06:42:58 +0900
> Subject: [PATCH 0/6] Convert code snippets to "listing" environment
> 
> Hi Paul,
> 
> So, this is another attempt to give code snippets their own environment.
> This time around, I used "float" and "subfig" packages.
> 
> The "ruled" style of "float" package (an example is presented in style
> guide) looks a bit different from that of "floatrow", but it should be OK.
> 
> Patch #4 gives examples of grouping floating objects.
> Grouping "ruled" style objects requires "subfig" package.
> 
> Patch #5 changes the label font in captions to bold face. It looks
> consistent with the looks of the "ruled" style.
> 
> Patch #6 does the conversion in the "memory barriers" section.
> The "ruled" style is not applied there yet. I'll submit a patch
> to change the default style if you think the look is OK.

Looks fine -- Listing D.2, correct?

I couldn't resist adding an epigraph.

							Thanx, Paul

>             Thanks, Akira
> --
> Akira Yokosawa (6):
>   Define 'listing' environment for style guide
>   styleguide: Add listing environment examples
>   Use 'subfig' package instead of 'subfigure'
>   styleguide: Add examples of grouping floating objects
>   Specify 'labelfont=bf' option in captionsetup
>   advsync: Convert code snippets and litmus tests to 'listing'
> 
>  advsync/memorybarriers.tex         | 120 ++++++++++++------------
>  appendix/styleguide/styleguide.tex | 184 +++++++++++++++++++++++++++++++++++--
>  perfbook.tex                       |   8 +-
>  3 files changed, 245 insertions(+), 67 deletions(-)
> 
> -- 
> 2.7.4
> 


  parent reply	other threads:[~2017-08-08 22:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 22:04 [PATCH 0/6] Convert code snippets to "listing" environment Akira Yokosawa
2017-08-08 22:06 ` [PATCH 1/6] Define 'listing' environment for style guide Akira Yokosawa
2017-08-08 22:07 ` [PATCH 2/6] styleguide: Add listing environment examples Akira Yokosawa
2017-08-08 22:08 ` [PATCH 3/6] Use 'subfig' package instead of 'subfigure' Akira Yokosawa
2017-08-08 22:10 ` [PATCH 4/6] styleguide: Add examples of grouping floating objects Akira Yokosawa
2017-08-08 22:11 ` [PATCH 5/6] Specify 'labelfont=bf' option in captionsetup Akira Yokosawa
2017-08-08 22:12 ` [PATCH 6/6] advsync: Convert code snippets and litmus tests to 'listing' Akira Yokosawa
2017-08-08 22:33 ` Paul E. McKenney [this message]
2017-08-08 22:44   ` [PATCH] Promote 'ruled' style as default of 'listing' environment Akira Yokosawa
2017-08-08 23:27     ` 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=20170808223314.GK3730@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