From: Richard Earnshaw <rearnsha@arm.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: DJ Delorie <dj@delorie.com>,
neroden@doctormoo.dyndns.org, gcc-patches@gcc.gnu.org,
binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
Richard.Earnshaw@arm.com
Subject: Re: toplevel Makefile.in: autogenerate more
Date: Wed, 25 Sep 2002 02:26:00 -0000 [thread overview]
Message-ID: <200209250925.g8P9PTs05484@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "24 Sep 2002 23:44:41 -0300." <orvg4ueqjq.fsf@free.redhat.lsd.ic.unicamp.br>
> On Sep 24, 2002, DJ Delorie <dj@delorie.com> wrote:
>
> > As much as I like automation, this rule is bad. Not everyone has
> > autogen, and those who don't shouldn't get penalized if they happen to
> > get the timestamps rearranged.
>
> If they use the recommended script, contrib/gcc_update, they'll get it
> right.
Not if you are updating gdb, or binutils it won't.
R.
prev parent reply other threads:[~2002-09-25 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 16:41 Nathanael Nerode
2002-09-24 16:46 ` DJ Delorie
2002-09-24 19:44 ` Alexandre Oliva
2002-09-25 2:26 ` Richard Earnshaw [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=200209250925.g8P9PTs05484@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@delorie.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@doctormoo.dyndns.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