From: Paolo Bonzini <bonzini@gnu.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: binutils@sourceware.org, gdb@sourceware.org, gcc@gnu.org,
DJ Delorie <dj@redhat.com>
Subject: Re: toplevel out of sync
Date: Tue, 25 May 2010 17:10:00 -0000 [thread overview]
Message-ID: <4BFC0489.4040904@gnu.org> (raw)
In-Reply-To: <20100525170912.GA21863@ins.uni-bonn.de>
On 05/25/2010 07:09 PM, Ralf Wildenhues wrote:
> * Paolo Bonzini wrote on Tue, May 25, 2010 at 06:06:16PM CEST:
>> the toplevel configury of gcc/gdb/binutils is very much out of sync.
>
>> Unfortunately I don't have much time to devote to bringing the trees
>> back in shape, and not even to chase down committers of patches
>> placed only on one side. Can anybody help with this?
>
> I can take a look.
>
>> ... the last date when the tree was synchronized ...
>
> It looked fairly good 3 months ago[1].
>
> Do you prefer tracking down committers and letting them finish their
> work, or should I just go ahead and sync sets of commits as I did last
> time?
As you prefer. I'd rather see a list of commits before giving you green
light though. :-)
Paolo
next prev parent reply other threads:[~2010-05-25 17:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 16:06 Paolo Bonzini
2010-05-25 17:09 ` Ralf Wildenhues
2010-05-25 17:10 ` Paolo Bonzini [this message]
2010-05-25 17:34 ` Ralf Wildenhues
2010-05-25 17:43 ` Ralf Wildenhues
2010-05-25 20:41 ` DJ Delorie
2010-05-26 4:39 ` Dave Korn
2010-05-26 4:49 ` Dave Korn
2010-05-26 5:16 ` [PATCH, committed] " Dave Korn
2010-05-26 6:25 ` Ralf Wildenhues
2010-05-26 7:30 ` Paolo Bonzini
2010-05-27 18:53 ` Ralf Wildenhues
2010-05-28 7:08 ` Paolo Bonzini
2010-06-01 17:36 ` Ralf Wildenhues
2010-06-01 17:59 ` Ralf Wildenhues
2010-05-25 20:38 ` DJ Delorie
2010-05-26 4:19 ` NightStrike
2010-05-26 4:35 ` Dave Korn
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=4BFC0489.4040904@gnu.org \
--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 \
/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