From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH v3 0/3] qqz and runlatex improvements
Date: Sat, 23 Apr 2016 22:05:52 -0700 [thread overview]
Message-ID: <20160424050552.GS3756@linux.vnet.ibm.com> (raw)
In-Reply-To: <571C1843.1060906@gmail.com>
On Sun, Apr 24, 2016 at 09:50:11AM +0900, Akira Yokosawa wrote:
> >From 687dd92a14a751c5919c80f9d7d8609db94d7634 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiysw@gmail.com>
> Date: Sun, 24 Apr 2016 09:26:52 +0900
> Subject: [PATCH v3 0/3] qqz and runlatex improvements
>
> Hi,
>
> There have been two issues that bother me a little since I began to
> build perfbook.pdf myself.
> One is the cross-link references of quick quizzes that land on random
> nearby places in the PDF.
> The other is the premature termination of make with warning messages
> displayed.
> I think I have managed to fix both issues.
>
> Paul tested v2 of this series and found that it is ready to be pushed
> out if minor fixes of a trailing blank and "XXXXXX" in commit messages
> are done.
Merged and pushed, thank you!
Thanx, Paul
> Changes since v2:
> Updated copyright notices in qqz.sty
> Removed a trailing blank in runfirstlatex.sh
> Fixed "XXXXXX" in commit messages
> Added "-f" option to "rm" in runlatex.sh
> Other minor changes in commit messages
>
> Changes since v1:
> Refactored runlatex.sh into 3 parts and improved the build behavior
> in response to the feedback's from Paul[1].
> As the result of the change, *.bbl files are not necessary any more,
> so a patch to remove them is added.
>
> [1] http://www.spinics.net/lists/perfbook/msg00160.html
>
> Akira Yokosawa (3):
> qqz: Improve accuracy of cross-links
> Improve behavior of build scripts
> Remove *.bbl from repository
>
> .gitignore | 2 +-
> Makefile | 55 +-
> perfbook-1c.bbl | 2103 -------------------------------------------
> perfbook-hb.bbl | 1949 ----------------------------------------
> perfbook.bbl | 2146 --------------------------------------------
> qqz.sty | 18 +-
> utilities/runfirstlatex.sh | 46 +
> utilities/runlatex.sh | 85 +-
> 8 files changed, 172 insertions(+), 6232 deletions(-)
> delete mode 100644 perfbook-1c.bbl
> delete mode 100644 perfbook-hb.bbl
> delete mode 100644 perfbook.bbl
> create mode 100644 utilities/runfirstlatex.sh
>
> --
> 1.9.1
>
prev parent reply other threads:[~2016-04-24 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 0:50 [PATCH v3 0/3] qqz and runlatex improvements Akira Yokosawa
2016-04-24 1:08 ` [PATCH v3 1/3] qqz: Improve accuracy of cross-links Akira Yokosawa
2016-04-24 3:50 ` Akira Yokosawa
2016-04-24 6:50 ` Akira Yokosawa
2016-04-24 14:23 ` Akira Yokosawa
2016-04-24 17:57 ` Paul E. McKenney
2016-04-24 22:19 ` Akira Yokosawa
2016-04-24 22:48 ` Paul E. McKenney
2016-04-25 12:34 ` Akira Yokosawa
2016-04-24 17:53 ` Paul E. McKenney
2016-05-09 12:07 ` Paolo Bonzini
2016-05-11 8:56 ` Paul E. McKenney
2016-04-24 1:10 ` [PATCH v3 2/3] Improve behavior of build scripts Akira Yokosawa
2016-04-24 1:12 ` [PATCH v3 3/3] Remove *.bbl from repository Akira Yokosawa
2016-04-24 5:05 ` 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=20160424050552.GS3756@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