From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14251 invoked by alias); 26 Oct 2005 00:29:33 -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 14224 invoked by uid 22791); 26 Oct 2005 00:29:25 -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; Wed, 26 Oct 2005 00:29:25 +0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 1122F47E79; Tue, 25 Oct 2005 17:29:23 -0700 (PDT) Date: Wed, 26 Oct 2005 06:45: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: <20051026002923.GC1155@adacore.com> References: <20051025222234.GE900@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/msg00202.txt.bz2 > Joel Brobecker writes: > > I would like to suggest that we post changes to the htdocs CVS repository > > to this mailing-list. That way, all developers have a chance to see and > > react to changes. This does not necessarily mean that we should go > > through the same formal process, with changelogs and all, but it would > > be nice to see the patches, with a short explaination containing the > > reason for the change if necessary. > > Do you mean posting the changes before they're committed, or after? I'm thinking after, but it's not a strong opinion. > If after, why not just set up an automatic patches list, as used for > the source code? 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... -- Joel