Discussions of the Parallel Programming book
 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 0/5] Misc updates
Date: Mon, 1 Oct 2018 08:18:10 -0700	[thread overview]
Message-ID: <20181001151810.GY4222@linux.ibm.com> (raw)
In-Reply-To: <1a19dbcb-3dbb-3359-dafa-1fc8dbe4837d@gmail.com>

On Mon, Oct 01, 2018 at 10:48:48PM +0900, Akira Yokosawa wrote:
> >From c545a33aea39aeae40bcff478285f814c32a4456 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Mon, 1 Oct 2018 22:05:58 +0900
> Subject: [PATCH 0/5] Misc updates
> 
> Hi Paul,
> 
> This is a miscellaneous collection of updates.
> 
> Patch #1 fixes build error you'd encounter when you do "make"
> after doing "make" under CodeSamples/ directory.
> 
> Patches #2 and #3 fix trivial typos in FAQ-BUILD.txt and
> tooldoftrade, respectively.
> 
> Patch #4 removes obsolete workaround code in perfbook.tex.
> 
> Patch #5 removes rules in Makefile used to support a hi-res
> figure in QC section.
> 
> Once Patch #5 is applied, you can remove orphaned files listed
> below:
> 
>     future/Bloch_Sphere.svg
>     future/QC-FormConstant.eps
>     future/QS1_1.svg
>     future/T2h1lc19xmqrdlsor.eps
>     future/ibmqx2-labeled.svg
> 
> As a matter of fact, I have prepared a patch to remove
> them, but it would be too large to submit.

Applied and queued them, along with a sixth patch to remove the above
files with your Suggested-by, thank you!!!

I never have tried it myself, but they say that the -D argument to
"git diff", "git show", and "git format-patch" will create a summarized
patch that can then be pulled in by "git am" and friends.  If either of
us remembers next time, we can try the experiment.  ;-)

							Thanx, Paul

>         Thanks, Akira
> --
> Akira Yokosawa (5):
>   CodeSamples: Exclude meta command lines in building api.h
>   FAQ-BUILD.txt: Fix typo
>   toolsoftrade: Fix typo DEFINE_PER_THREAD() -> DEFINE_PER_CPU()
>   Remove workaround for Fedora 23 Tex Live bug
>   Makefile: Remove rules for QC section
> 
>  .gitignore                    |  1 -
>  CodeSamples/Makefile          |  4 +++-
>  FAQ-BUILD.txt                 |  2 +-
>  Makefile                      | 25 +++++--------------------
>  perfbook.tex                  | 14 --------------
>  toolsoftrade/toolsoftrade.tex |  2 +-
>  utilities/gen_snippet_d.pl    | 16 ++++++++--------
>  7 files changed, 18 insertions(+), 46 deletions(-)
> 
> -- 
> 2.7.4
> 


  parent reply	other threads:[~2018-10-01 21:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 13:48 [PATCH 0/5] Misc updates Akira Yokosawa
2018-10-01 13:50 ` [PATCH 1/5] CodeSamples: Exclude meta command lines in building api.h Akira Yokosawa
2018-10-01 13:51 ` [PATCH 2/5] FAQ-BUILD.txt: Fix typo Akira Yokosawa
2018-10-01 13:53 ` [PATCH 3/5] toolsoftrade: Fix typo DEFINE_PER_THREAD() -> DEFINE_PER_CPU() Akira Yokosawa
2018-10-01 13:55 ` [PATCH 4/5] Remove workaround for Fedora 23 Tex Live bug Akira Yokosawa
2018-10-01 13:56 ` [PATCH 5/5] Makefile: Remove rules for QC section Akira Yokosawa
2018-10-01 15:18 ` Paul E. McKenney [this message]
2018-10-01 15:26   ` [PATCH 0/5] Misc updates Akira Yokosawa
2018-10-01 15:34     ` 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=20181001151810.GY4222@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox