From: Paolo Bonzini <bonzini@gnu.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Paolo Bonzini <bonzini@gnu.org>, Nick Clifton <nickc@redhat.com>,
"Naveen.H.S" <naveen.S@kpitcummins.com>,
binutils@sourceware.org, gdb@sourceware.org, gcc@gnu.org,
DJ Delorie <dj@redhat.com>
Subject: Re: toplevel *again* out of sync
Date: Sat, 02 Oct 2010 14:03:00 -0000 [thread overview]
Message-ID: <AANLkTik3Ft2-kTpNRCsF2mTvKwT4o1s=pRLdbSH7dVgk@mail.gmail.com> (raw)
In-Reply-To: <20101002124037.GB3029@gmx.de>
> Other than that, below is the combined patch I intend to commit to src
> unless there are disagreements.
Ok, thanks.
DJ, can you amend your scripts so that the head of gcc/ChangeLog and
src/ChangeLog is included? This will make it easier to bug relevant
people.
Paolo
next prev parent reply other threads:[~2010-10-02 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 8:47 Paolo Bonzini
2010-10-02 9:18 ` Ralf Wildenhues
2010-10-02 12:40 ` Ralf Wildenhues
2010-10-02 14:03 ` Paolo Bonzini [this message]
2010-10-03 7:59 ` DJ Delorie
2010-10-04 8:44 ` Naveen H. S
2010-10-07 19:27 ` 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='AANLkTik3Ft2-kTpNRCsF2mTvKwT4o1s=pRLdbSH7dVgk@mail.gmail.com' \
--to=bonzini@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=gcc@gnu.org \
--cc=gdb@sourceware.org \
--cc=naveen.S@kpitcummins.com \
--cc=nickc@redhat.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