From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/2] Makefile cleanups
Date: Fri, 14 Oct 2016 07:51:10 -0700 [thread overview]
Message-ID: <20161014145110.GD29518@linux.vnet.ibm.com> (raw)
In-Reply-To: <dee02541-574c-3686-8dc7-5cb02303a408@gmail.com>
On Fri, Oct 14, 2016 at 07:05:35AM +0900, Akira Yokosawa wrote:
> >From 3fc3583818c9103ef2d1c01516b362c4b6768604 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Thu, 13 Oct 2016 20:51:46 +0900
> Subject: [PATCH 0/2] Makefile cleanups
>
> Hi,
>
> Here is a patch set sequel to commit 0e6e192e6ea7 ("Makefile: Use
> implicit rules for various layout options").
>
> 1st patch shortens some rules by using automatic variables.
> 2nd one gets rid of apparent dependency rules like "1c: perfbook-1c.pdf"
> by using secondary-expansion feature of GNU make.
>
> Now almost all redundant rules have been removed.
> There is no change in the behavior of make command.
>
> This set is a by-product of my attempt to try some alternative monospace
> fonts to be used among Times Roman text. To give you an easy way to
> compare candidates, I'm preparing patches to add a few make targets, but
> not sure where it goes. This cleanup set seems worthwhile on its own.
>
> Thanks, Akira
>
> Akira Yokosawa (2):
> Makefile: Use more automatic variables
> Makefile: Use seconday expansion
>
> .gitignore | 7 ++-----
> Makefile | 28 ++++++++++++++--------------
> 2 files changed, 16 insertions(+), 19 deletions(-)
Applied and pushed, thank you!
Thanx, Paul
prev parent reply other threads:[~2016-10-14 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 22:05 [PATCH 0/2] Makefile cleanups Akira Yokosawa
2016-10-13 22:07 ` [PATCH 1/2] Makefile: Use more automatic variables Akira Yokosawa
2016-10-13 22:08 ` [PATCH 2/2] Makefile: Use secondary expansion Akira Yokosawa
2016-10-14 14:51 ` 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=20161014145110.GD29518@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