From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: git@vger.kernel.org
Subject: Re: [PATCH] Include Makefile.localdef in Makefile, if it exists.
Date: Fri, 02 Dec 2005 22:35:17 -0800 [thread overview]
Message-ID: <3061.1133591717@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <Pine.LNX.4.63.0512030322410.19086@wbgn013.biozentrum.uni-wuerzburg.de>
And Johannes Schindelin writes:
- I wonder why you do not just override them in config.mak, which was
- introduced just for that purpose...
'Cause I'm a git and didn't notice it, thanks. The prefix stuff
probably ought to be moved below the -include config.mak so
someone need only change $(prefix) and not the rest. I might
send along such a patch, along with a note about config.mak in
INSTALL...
Jason
next prev parent reply other threads:[~2005-12-03 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 23:11 [PATCH] Include Makefile.localdef in Makefile, if it exists Jason Riedy
2005-12-03 2:23 ` Johannes Schindelin
2005-12-03 6:35 ` Jason Riedy [this message]
2005-12-03 10:45 ` Johannes Schindelin
2005-12-03 19:14 ` Junio C Hamano
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=3061.1133591717@lotus.CS.Berkeley.EDU \
--to=ejr@eecs.berkeley.edu \
--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).