From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4793 invoked by alias); 22 Feb 2003 00:53:45 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4696 invoked from network); 22 Feb 2003 00:53:45 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 22 Feb 2003 00:53:45 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5D0542EF9; Fri, 21 Feb 2003 19:58:23 -0500 (EST) Message-ID: <3E56CB2F.1080502@redhat.com> Date: Sat, 22 Feb 2003 00:53:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard.Earnshaw@arm.com Cc: Daniel Jacobowitz , Jim Blandy , gdb@sources.redhat.com Subject: Re: [maint] The GDB maintenance process References: <200302201832.h1KIWCq05909@pc960.cambridge.arm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00491.txt.bz2 > -Branches should have an owner. > The owner can set further policy for a branch, but may not change the > ground rules. In particular, they can set a policy for commits (be it > adding more reviewers or deciding who can commit). Yep. > -All commits to a branch must be covered by an assignment > This saves us from the situation where a branch might become contaminated. Um, er, yes, `obviously' (How did I forget that one :-( :-). Andrew