From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/3] fix minor Makefile annoyances
Date: Fri, 29 May 2015 03:21:19 -0400 [thread overview]
Message-ID: <20150529072119.GA5415@peff.net> (raw)
I've noticed that running "make" on a fully-built git tree still builds
a lot of things:
$ make >/dev/null 2>&1 && make
GEN perl/PM.stamp
SUBDIR gitweb
GEN git-add--interactive
GEN git-difftool
GEN git-archimport
GEN git-cvsexportcommit
GEN git-cvsimport
GEN git-cvsserver
GEN git-relink
GEN git-send-email
GEN git-svn
GEN git-p4
SUBDIR ../
make[2]: 'GIT-VERSION-FILE' is up to date.
GEN git-instaweb
SUBDIR perl
SUBDIR templates
Here it is after this series:
$ make >/dev/null 2>&1 && make
SUBDIR perl
SUBDIR templates
The patches are:
[1/3]: Makefile: drop dependency between git-instaweb and gitweb
[2/3]: Makefile: avoid timestamp updates to GIT-BUILD-OPTIONS
[3/3]: Makefile: silence perl/PM.stamp recipe
-Peff
next reply other threads:[~2015-05-29 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 7:21 Jeff King [this message]
2015-05-29 7:25 ` [PATCH 1/3] Makefile: drop dependency between git-instaweb and gitweb Jeff King
2015-05-29 7:26 ` [PATCH 2/3] Makefile: avoid timestamp updates to GIT-BUILD-OPTIONS Jeff King
2015-05-29 7:26 ` [PATCH 3/3] Makefile: silence perl/PM.stamp recipe Jeff King
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=20150529072119.GA5415@peff.net \
--to=peff@peff.net \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).