From: Ben Elliston <bje@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: Maintainer mode
Date: Sat, 09 Sep 2000 01:48:00 -0000 [thread overview]
Message-ID: <14777.45927.15830.37734@walkabout.cygnus.com> (raw)
In-Reply-To: <14777.27737.706634.552352@casey.transmeta.com>
Doug Evans writes:
> > The advantages here are obvious: you need not remember an extra option
> > to `configure' and it works more obviously.
> I recognize the reasons why one would want to do this.
> I didn't do this because it carries extra burdens I wasn't prepared
> to dump on binutils/gdb people.
This burden only exists when the modification times of the .cpu files
is newer than the generated files. The same burden could be said for
people building GCC and requiring Bison because a source distribution
has generated C files that are older than the `.y' file. If it is
carefully managed, I don't think this will affect anyone. Do you
agree?
Ben
next prev parent reply other threads:[~2000-09-09 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-08 15:35 Ben Elliston
2000-09-08 15:47 ` Doug Evans
2000-09-08 15:52 ` Doug Evans
2000-09-09 1:48 ` Ben Elliston [this message]
2000-09-09 12:21 ` Doug Evans
[not found] ` <20000908184128.B29784@redhat.com>
2000-09-09 1:48 ` Ben Elliston
2000-09-09 2:00 ` Eric Christopher
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=14777.45927.15830.37734@walkabout.cygnus.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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 read-only IMAP folder(s) and NNTP newsgroup(s).