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/5] Style guide updates
Date: Sun, 13 Aug 2017 10:26:24 -0700	[thread overview]
Message-ID: <20170813172624.GA7017@linux.vnet.ibm.com> (raw)
In-Reply-To: <cc6fbe48-4598-922c-295b-a5d70a7d859d@gmail.com>

On Sun, Aug 13, 2017 at 12:27:52PM +0900, Akira Yokosawa wrote:
> >From 24d4de52c8186c1ec1787e76d13e22646d804a53 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Sun, 13 Aug 2017 11:00:48 +0900
> Subject: [PATCH 0/5] Style guide updates
> 
> Hi Paul,
> 
> The style guide needs some updates regarding recent changes in
> litmus tests in memory barriers section. (Patch #3)
> Also I recovered the tweaks in table layout. I added another
> option to color rows alternately. (Patch #1 and #2)
> Patch #4 is my attempt to convince you that using commas for
> digit grouping should be regarded as harmful in global POV.
> My suggestion is to use \num{} commands in LaTeX source and
> let a reader to pick a style of his/her choice.
> 
> \num{} command can slow down pdflatex processing somewhat,
> but should be acceptable on modern platforms.
> 
> Thoughts?

Applied and pushed, thank you!

Table D.3 looks fine, but it only has thee columns.  If it had more
columns or was wider or variable-depth rows, it would be hard to read.
Table D.4 looks good to me, but I (intentionally) have not yet looked
at what you had to do in LaTeX to make it happen.  ;-)

							Thanx, Paul

>         Thanks, Akira
> --
> Akira Yokosawa (5):
>   styleguide: Add examples of alternative table layout
>   styleguide: Tweak layout of 'Limitation' table
>   styleguide: Update LaTeX source of code snippet
>   styleguide: Add example of options to \num{} command
>   styleguide: Emphasize source part of epigraph
> 
>  appendix/styleguide/samplecodesnippet.tex    |  19 --
>  appendix/styleguide/samplecodesnippetfig.tex |  19 ++
>  appendix/styleguide/samplecodesnippetlst.tex |  19 ++
>  appendix/styleguide/styleguide.tex           | 375 ++++++++++++++++++---------
>  perfbook.tex                                 |   5 +-
>  5 files changed, 301 insertions(+), 136 deletions(-)
>  delete mode 100644 appendix/styleguide/samplecodesnippet.tex
>  create mode 100644 appendix/styleguide/samplecodesnippetfig.tex
>  create mode 100644 appendix/styleguide/samplecodesnippetlst.tex
> 
> -- 
> 2.7.4
> 


  parent reply	other threads:[~2017-08-13 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13  3:27 [PATCH 0/5] Style guide updates Akira Yokosawa
2017-08-13  3:29 ` [PATCH 1/5] styleguide: Add examples of alternative table layout Akira Yokosawa
2017-08-13  3:30 ` [PATCH 2/5] styleguide: Tweak layout of 'Limitation' table Akira Yokosawa
2017-08-13  3:31 ` [PATCH 3/5] styleguide: Update LaTeX source of code snippet Akira Yokosawa
2017-08-13  3:32 ` [PATCH 4/5] styleguide: Add example of options to \num{} command Akira Yokosawa
2017-08-13  3:33 ` [PATCH 5/5] styleguide: Emphasize source part of epigraph Akira Yokosawa
2017-08-13 17:26 ` Paul E. McKenney [this message]
2017-08-13 23:24   ` [PATCH 0/5] Style guide updates Akira Yokosawa
2017-08-14 15:32     ` 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=20170813172624.GA7017@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