From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12181 invoked by alias); 28 Oct 2005 18:10:56 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12159 invoked by uid 22791); 28 Oct 2005 18:10:49 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 28 Oct 2005 18:10:49 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EVYgd-00086O-NO; Fri, 28 Oct 2005 14:10:43 -0400 Date: Fri, 28 Oct 2005 18:16:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: Jim Blandy , gdb-patches@sources.redhat.com Subject: Re: suggestion for future changes to GDB website Message-ID: <20051028181043.GA31049@nevyn.them.org> Mail-Followup-To: Joel Brobecker , Jim Blandy , gdb-patches@sources.redhat.com References: <20051025222234.GE900@adacore.com> <20051026002923.GC1155@adacore.com> <20051028180325.GT1155@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051028180325.GT1155@adacore.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00213.txt.bz2 On Fri, Oct 28, 2005 at 11:03:25AM -0700, Joel Brobecker wrote: > All the developers who answered were in favor of posting the changes > one way or the other. Let's agree on one of the following forms: > > 1. Post patch to gdb-patches BEFORE checkin > Not sure how to make things work: Approval needed? Etc. > > 2. Post patch to gdb-patches AFTER checkin > > 3. Have an automated system that sends the patch with RH to > a mailing-list. Could be a dedicated mailing-list, or one > of the GDB existing mailing lists. > > I'm OK with either of the proposals. How about just treating it like part of GDB? Allow global maintainers to make or approve changes, and list it in MAINTAINERS. -- Daniel Jacobowitz CodeSourcery, LLC