From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-37441-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27661 invoked by alias); 26 May 2010 04:19:29 -0000
Received: (qmail 27646 invoked by uid 22791); 26 May 2010 04:19:28 -0000
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0	tests=AWL,BAYES_40,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_SV
X-Spam-Check-By: sourceware.org
Received: from mail-qy0-f175.google.com (HELO mail-qy0-f175.google.com) (209.85.221.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 26 May 2010 04:19:25 +0000
Received: by qyk5 with SMTP id 5so8910301qyk.3        for <multiple recipients>; Tue, 25 May 2010 21:19:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.94.65 with SMTP id y1mr4632080qam.136.1274847563026; Tue, 	25 May 2010 21:19:23 -0700 (PDT)
Received: by 10.229.84.147 with HTTP; Tue, 25 May 2010 21:19:22 -0700 (PDT)
In-Reply-To: <201005252038.o4PKcYGB023708@greed.delorie.com>
References: <4BFBF578.40904@gnu.org>	 <201005252038.o4PKcYGB023708@greed.delorie.com>
Date: Wed, 26 May 2010 04:19:00 -0000
Message-ID: <AANLkTilK_qEk0TpL8T1NubcewMQjlq3Ngi_PD-JZjrgv@mail.gmail.com>
Subject: Re: toplevel out of sync
From: NightStrike <nightstrike@gmail.com>
To: DJ Delorie <dj@redhat.com>
Cc: Paolo Bonzini <bonzini@gnu.org>, binutils@sourceware.org, gdb@sourceware.org, 	gcc@gnu.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2010-05/txt/msg00081.txt.bz2

On Tue, May 25, 2010 at 4:38 PM, DJ Delorie <dj@redhat.com> wrote:
>
>> 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. =A0Is there any agreement on this?
>
> Our current policy certainly doesn't work, either we come up with
> something that will, or abandon the whole idea and let chaos reign.

Ideas:
Switch to svn and use svn:externals to link the two repos
Make binutils be part of the gcc repository to begin with
Lock the files on the binutils side and only allow a specific user to
commit; Make that user a bot that's hooked onto the gcc commit