Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: binutils@sourceware.org, gdb@sourceware.org, gcc@gnu.org,
	 DJ Delorie <dj@redhat.com>
Subject: toplevel out of sync
Date: Tue, 25 May 2010 16:06:00 -0000	[thread overview]
Message-ID: <4BFBF578.40904@gnu.org> (raw)

All,

the toplevel configury of gcc/gdb/binutils is very much out of sync.

If people agree, I would like to freeze commits to the toplevel 
configury until they are not diverging anymore.

Also, I would like to make a new policy that from now on patches to the 
toplevel cannot be committed by anyone who doesn't have write access to 
both gcc and src.  Is there any agreement on this?

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?  In particular, if DJ 
could provide with the last date when the tree was synchronized that 
would help.

Paolo


             reply	other threads:[~2010-05-25 16:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 16:06 Paolo Bonzini [this message]
2010-05-25 17:09 ` Ralf Wildenhues
2010-05-25 17:10   ` Paolo Bonzini
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=4BFBF578.40904@gnu.org \
    --to=bonzini@gnu.org \
    --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