From: Nix <nix@esperi.org.uk>
To: Mike Frysinger <vapier@gentoo.org>
Cc: 7eggert@gmx.de, Karel Zak <kzak@redhat.com>,
List util-linux-ng <util-linux-ng@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng 2.13-rc1
Date: Thu, 05 Jul 2007 22:34:16 +0100 [thread overview]
Message-ID: <878x9ucz6v.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <200707051730.25776.vapier@gentoo.org> (Mike Frysinger's message of "Thu, 5 Jul 2007 17:30:24 -0400")
On 5 Jul 2007, Mike Frysinger outgrape:
> On Thursday 05 July 2007, Bodo Eggert wrote:
>> The Makefiles generated by autotools is a huge mess, if autotools got it
>> wrong (again!), fixing them requires editing a lot of files.
>
> this looks like a no brainer to me: dont edit generated files
There is a worthwhile point here: if your input to the makefile
generator is buggy and make errors out, you'll have to look at the
generated code in order to relate the make error to the original.
(It's not that hard with automake, admittedly, but make should
really have a #line analogue to help. It could be much worse, as
anyone who ever tried to use Knuth's old WEAVE tool would know.
At least automake doesn't intentionally obfuscate the makefiles
it emits...)
--
`... in the sense that dragons logically follow evolution so they would
be able to wield metal.' --- Kenneth Eng's colourless green ideas sleep
furiously
next prev parent reply other threads:[~2007-07-05 21:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8CYT9-4Ou-23@gated-at.bofh.it>
[not found] ` <8Dh9k-8lT-3@gated-at.bofh.it>
[not found] ` <8DtDz-3xC-15@gated-at.bofh.it>
2007-07-05 14:50 ` Bodo Eggert
2007-07-05 19:20 ` DervishD
2007-07-05 20:42 ` Nix
2007-07-05 20:55 ` Bernhard Walle
2007-07-06 6:42 ` Nix
2007-07-06 7:19 ` Mike Frysinger
2007-07-06 22:43 ` Nix
2007-07-06 6:41 ` DervishD
2007-07-06 7:17 ` Mike Frysinger
2007-07-06 10:43 ` DervishD
2007-07-06 12:17 ` Bodo Eggert
2007-07-06 12:51 ` DervishD
2007-07-05 20:36 ` Nix
2007-07-05 21:30 ` Mike Frysinger
2007-07-05 21:34 ` Nix [this message]
2007-07-05 21:47 ` Mike Frysinger
2007-07-06 0:30 ` Bryan Henderson
2007-07-06 1:16 ` Mike Frysinger
2007-07-06 16:50 ` Bryan Henderson
2007-07-03 22:11 Karel Zak
2007-07-04 8:42 ` Christoph Hellwig
2007-07-04 10:34 ` David Miller
2007-07-05 16:41 ` Mike Frysinger
2007-07-05 18:04 ` Andreas Dilger
2007-07-05 21:30 ` Karel Zak
2007-07-06 0:38 ` Matthew Wilcox
2007-07-05 23:03 ` Jeff Garzik
2007-07-06 9:01 ` Gerd Hoffmann
2007-07-06 9:16 ` Jeff Garzik
2007-07-06 19:35 ` Joel Becker
2007-07-09 7:20 ` Gerd Hoffmann
2007-07-09 20:18 ` Mike Frysinger
2007-07-04 11:11 ` Jan Engelhardt
2007-07-05 17:22 ` H. Peter Anvin
2007-07-04 17:47 ` DervishD
2007-07-05 7:01 ` Nix
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=878x9ucz6v.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=7eggert@gmx.de \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux-ng@vger.kernel.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®