From: Tom Tromey <tromey@redhat.com>
To: Anthony Green <green@moxielogic.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Patch] merge config.sub from upstream
Date: Tue, 29 Jul 2014 15:14:00 -0000 [thread overview]
Message-ID: <87ppgocjl7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <871tt45ssq.fsf@moxielogic.com> (Anthony Green's message of "Tue, 29 Jul 2014 07:05:25 -0400")
>>>>> "Anthony" == Anthony Green <green@moxielogic.com> writes:
Anthony> I'm committing this change on the assumption that upstream
Anthony> config.{sub|guess} merges are auto-approved, as is done in GCC. This
Anthony> brings binutils-gdb in line with upstream config and GCC sources.
Just FYI I think it's the norm to courtesy CC binutils.
Tom
prev parent reply other threads:[~2014-07-29 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 12:10 Anthony Green
2014-07-29 15:14 ` Tom Tromey [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=87ppgocjl7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=green@moxielogic.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