From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2566 invoked by alias); 28 Oct 2005 18:03:36 -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 2501 invoked by uid 22791); 28 Oct 2005 18:03:27 -0000 Received: from s142-179-108-108.bc.hsia.telus.net (HELO takamaka.act-europe.fr) (142.179.108.108) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 28 Oct 2005 18:03:27 +0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 1A84547E6B; Fri, 28 Oct 2005 11:03:25 -0700 (PDT) Date: Fri, 28 Oct 2005 18:10:00 -0000 From: Joel Brobecker To: Jim Blandy Cc: gdb-patches@sources.redhat.com Subject: Re: suggestion for future changes to GDB website Message-ID: <20051028180325.GT1155@adacore.com> References: <20051025222234.GE900@adacore.com> <20051026002923.GC1155@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-SW-Source: 2005-10/txt/msg00212.txt.bz2 > > That's an option. The nice thing about posting the patch here is that > > you can add an explaination to the patch. Revision histories are > > sometimes a bit obscure... > > What would you want to put in an explanation that doesn't belong in a > log entry? Most of the time, the RH will contain everything necessary, so nothing more will be added. I don't have any example offhand of when an explanation need to complete the RH. Perhaps after making a change on which you want to start a discussion. I think both formats are going to work. Whichever people want, I'm ok, as long as we see the changes being made, and that we get a chance of reacting to them. 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. -- Joel