From: Tom Tromey <tromey@redhat.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: Samuel Bronson <naesten@gmail.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: Update rebuild rules in non-automake directories.
Date: Wed, 29 Jul 2009 18:37:00 -0000 [thread overview]
Message-ID: <m3hbwvwde3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090729053050.GC28894@gmx.de> (Ralf Wildenhues's message of "Wed\, 29 Jul 2009 07\:30\:50 +0200")
>>>>> "Ralf" == Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
Ralf> About the changes that should go upstream, are you saying I should get
Ralf> them accepted upstream before they can go into gdb / src? Please note
Ralf> that several of the changes are specific to GCC/src; for example,
Ralf> m4_rename_force would require boehm-gc to move to Autoconf 2.64, or to
Ralf> employ the workaround we add to override.m4, somewhere in its code.
We already dealt with this, but for the record, I think it is best to at
least make an attempt to send things upstream before checking in a local
divergence. This helps make future imports less hairy. If upstream
takes too long, for whatever reason, then IMO it is usually ok to just
go ahead (particularly for configury stuff, which tends not to be very
invasive).
Tom
next prev parent reply other threads:[~2009-07-29 18:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090628183334.GA5401@gmx.de>
2009-07-28 18:54 ` Ralf Wildenhues
2009-07-28 19:51 ` Paolo Bonzini
2009-07-28 21:35 ` Tom Tromey
2009-07-29 3:09 ` Samuel Bronson
2009-07-29 5:31 ` Tom Tromey
2009-07-29 16:15 ` Ralf Wildenhues
2009-07-29 18:35 ` Samuel Bronson
2009-07-29 18:37 ` Tom Tromey [this message]
2009-07-30 21:27 ` Ralf Wildenhues
[not found] ` <20090730210952.GD24465__15749.4424529888$1248988226$gmane$org@gmx.de>
2009-07-30 21:30 ` Tom Tromey
2009-07-29 15:16 ` Ben Elliston
2009-08-26 16:29 ` Jan Kratochvil
2009-08-26 16:54 ` Ralf Wildenhues
2009-08-26 17:10 ` Jan Kratochvil
2009-08-26 17:51 ` Ralf Wildenhues
2009-08-26 17:57 ` Eli Zaretskii
2009-08-26 19:13 ` Jan Kratochvil
2009-08-31 20:42 ` obtaining configure args from config.status (was: Update rebuild rules in non-automake directories.) Ralf Wildenhues
2009-09-01 1:10 ` obtaining configure args from config.status Paolo Bonzini
2009-09-06 18:15 ` obtaining configure args from config.status (was: Update rebuild rules in non-automake directories.) Ralf Wildenhues
2009-09-08 18:37 ` obtaining configure args from config.status Tom Tromey
2009-09-08 16:28 ` Jan Kratochvil
2009-09-08 18:26 ` Ralf Wildenhues
2009-09-08 18:38 ` Tom Tromey
2009-09-08 18:51 ` Ralf Wildenhues
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=m3hbwvwde3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=naesten@gmail.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