From: "Brian O'Mahoney" <omb@khandalf.com>
To: git@vger.kernel.org
Subject: Handover, Make
Date: Thu, 28 Jul 2005 01:08:03 +0200 [thread overview]
Message-ID: <42E813D3.7020804@khandalf.com> (raw)
First, congratulations Junio, on taking over this stuff, and all the best.
Second, the killer argument, in the 'Recursive Make ... harmful' is the
basic one that Recursive Makes breaks up the dependancy graph, and
almost guarentees that it is wrong unless you do a lot of work to fix
that artifact. Now git is small enough that make clean; make won't take
too long but git is also a basis for other layers, so there is good
reason to try to get it right.
--
mit freundlichen Grüßen, Brian.
next reply other threads:[~2005-07-27 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 23:08 Brian O'Mahoney [this message]
2005-07-28 7:54 ` Handover, Make Petr Baudis
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=42E813D3.7020804@khandalf.com \
--to=omb@khandalf.com \
--cc=git@vger.kernel.org \
--cc=omb@bluewin.ch \
/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).