From: Timo Hirvonen <tihirvon@gmail.com>
To: Ryan Anderson <ryan@michonline.com>
Cc: pasky@suse.cz, martin.langhoff@gmail.com, git@vger.kernel.org
Subject: Re: [RFC+PATCH 1/1] Move SCM interoperability tools into scm/
Date: Mon, 10 Jul 2006 12:45:25 +0300 [thread overview]
Message-ID: <20060710124525.54ecaeab.tihirvon@gmail.com> (raw)
In-Reply-To: <44B19D42.6030701@michonline.com>
Ryan Anderson <ryan@michonline.com> wrote:
> By "don't split the Makefile", do mean, "Don't use recursive make"?
>
> I'm fine with that (and if you look at my patch, I "include
> scm/Makefile" to do just that), but if you mean "keep only a top-level
> Makefile", well, I think that continues the problem of "there is too
> much stuff going on here", but I can be persuaded otherwise.
Recursive make is a horrible hack. Splitting Makefile to smaller chunks
which would be included in the top level Makefile is almost as bad. You
can't cd to subdirectory and run make there and you have to prefix all
files with "subdir/".
If you really want to make Makefile shorter just move all the platform
specific stuff to a configure script.
--
http://onion.dynserv.net/~timo/
prev parent reply other threads:[~2006-07-10 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 6:17 [RFC+PATCH 1/1] Move SCM interoperability tools into scm/ Ryan Anderson
2006-07-09 14:31 ` Johannes Schindelin
2006-07-09 21:26 ` Martin Langhoff
2006-07-09 22:13 ` Petr Baudis
2006-07-09 22:21 ` Johannes Schindelin
2006-07-09 22:23 ` Ryan Anderson
2006-07-10 0:39 ` Junio C Hamano
2006-07-10 3:24 ` Ryan Anderson
2006-07-09 22:34 ` Timo Hirvonen
2006-07-10 0:20 ` Ryan Anderson
2006-07-10 9:45 ` Timo Hirvonen [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=20060710124525.54ecaeab.tihirvon@gmail.com \
--to=tihirvon@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=pasky@suse.cz \
--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).