From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [GIT PULL FOR TEST v2] Another round of build script tweaks
Date: Thu, 5 May 2016 00:39:22 +0900 [thread overview]
Message-ID: <3d253c44-5f0d-a809-119d-70f0ba38000e@gmail.com> (raw)
Hi, Paul.
Finally, I set up a GitHub account, and pushed v2 of the series
"Another round of build script tweaks".
Please pull this into your local test branch and take time to see if
it actually works as you would expect. I'm fairly certain there would
be some regression, especially in the final commit 92ae43c3a72a
("Further improvement of build scripts").
I'm also concerned about the fix of sig-theft.dot.
Changes from v1.
Reorganized the entire series so that minor changes would come
first.
Note: While I set up the account, I noticed a typo in my git-config
setting of user.email. My email address in the commit messages so
far was wrong. Sorry for the slip-up...
Thanks, Akira
---
The following changes since commit 3f8bb7d620edee44637be00ba738761a4fc0732e:
.gitignore: Add planned empty targets (2016-05-03 17:49:50 -0700)
are available in the git repository at:
https://github.com/akiyks/perfbook.git makefile-tweaks-v2
for you to fetch changes up to 92ae43c3a72a3bcd7fd99ac681209ceafc6d7e65:
Further improvement of build scripts (2016-05-04 23:43:06 +0900)
----------------------------------------------------------------
Akira Yokosawa (7):
Add font installation check
Add short name targets in Makefile
sig-theft: Fix .dot source for dot - graphviz version 2.36.0
Make default target of "make" overridable
Makefile: Reorder rules
Makefile: Use wildcards
Further improvement of build scripts
.gitignore | 1 -
FAQ.txt | 23 ++++
Makefile | 336 ++++++++++++++++++-------------------------------
count/sig-theft.dot | 17 +--
count/sig-theft.eps | 338 +++++++++++++++++++++++---------------------------
utilities/eps2pdf.sh | 12 ++
utilities/runlatex.sh | 9 ++
7 files changed, 333 insertions(+), 403 deletions(-)
next reply other threads:[~2016-05-04 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 15:39 Akira Yokosawa [this message]
2016-05-04 23:35 ` [GIT PULL FOR TEST v2] Another round of build script tweaks Akira Yokosawa
2016-05-05 13:21 ` Paul E. McKenney
2016-05-05 23:47 ` Akira Yokosawa
2016-05-06 11:09 ` Paul E. McKenney
2016-05-07 0:06 ` [GIT PULL v3] " Akira Yokosawa
2016-05-07 13:20 ` Paul E. McKenney
2016-05-07 15:23 ` Akira Yokosawa
2016-05-11 9:17 ` Paul E. McKenney
2016-05-11 14:34 ` [GIT PULL v4] " Akira Yokosawa
2016-05-14 9:55 ` 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=3d253c44-5f0d-a809-119d-70f0ba38000e@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@linux.vnet.ibm.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.