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
Subject: Re: toplevel out of sync
Date: Wed, 26 May 2010 04:19:00 -0000 [thread overview]
Message-ID: <AANLkTilK_qEk0TpL8T1NubcewMQjlq3Ngi_PD-JZjrgv@mail.gmail.com> (raw)
In-Reply-To: <201005252038.o4PKcYGB023708@greed.delorie.com>
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. Is 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
next prev parent reply other threads:[~2010-05-26 4:19 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
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 [this message]
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=AANLkTilK_qEk0TpL8T1NubcewMQjlq3Ngi_PD-JZjrgv@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.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