From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Ryan Anderson <ryan@michonline.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] "Recursive Make considered harmful"
Date: Wed, 27 Jul 2005 18:07:07 -0400 [thread overview]
Message-ID: <42E8058B.7070907@gmail.com> (raw)
In-Reply-To: <7v4qafrk8w.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> While I do not have strong objections to make the build process
> go faster, it is somewhat disturbing that the Makefile pieces
> maintained in subdirectories need to name things they touch
> using paths that include the subdirectory names. I do not have
> a better alternative to suggest, though...
For a project the size of Git, is there any real benefit to this change?
Besides pathing issues, you also have to aware that all identifiers in
the included makefile fragments will be global.
I don't object to the change but I see it as trading one maintenance
issue for another.
next prev parent reply other threads:[~2005-07-27 22:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 8:39 [PATCH/RFC] "Recursive Make considered harmful" Ryan Anderson
2005-07-27 14:25 ` A Large Angry SCM
2005-07-27 14:37 ` Kirby C. Bohling
2005-07-27 15:32 ` A Large Angry SCM
2005-07-27 21:50 ` Junio C Hamano
2005-07-27 22:07 ` A Large Angry SCM [this message]
2005-07-28 7:51 ` Petr Baudis
2005-07-28 9:40 ` Matthias Urlichs
2005-07-28 7:04 ` Junio C Hamano
2005-07-28 7:45 ` Matthias Urlichs
2005-07-28 16:38 ` Junio C Hamano
2005-07-28 17:09 ` A Large Angry SCM
2005-07-29 6:53 ` Ryan Anderson
2005-07-29 7:31 ` Sam Ravnborg
2005-07-29 7:46 ` Petr Baudis
2005-07-29 9:12 ` Timo Hirvonen
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=42E8058B.7070907@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ryan@michonline.com \
/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).