From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9323 invoked by alias); 11 Feb 2003 10:20:41 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 9316 invoked from network); 11 Feb 2003 10:20:41 -0000 Received: from unknown (HELO mail.libertysurf.net) (213.36.80.91) by 172.16.49.205 with SMTP; 11 Feb 2003 10:20:41 -0000 Received: from localhost.localdomain (212.83.191.215) by mail.libertysurf.net (6.5.026) id 3DE3A33200AFF6DB; Tue, 11 Feb 2003 11:20:28 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Eric Botcazou To: Gerald Pfeifer Subject: Re: ChangeLog conventions (was: hppa-linux regressions and 3.2.2 release) Date: Tue, 11 Feb 2003 10:20:00 -0000 User-Agent: KMail/1.4.3 Cc: Franz Sirl , Gabriel Dos Reis , Randolph Chung , gcc@gcc.gnu.org References: <5.2.0.9.2.20030203121659.01b62790@mail.lauterbach.com> <200302031430.15093.ebotcazou@libertysurf.fr> In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200302111121.06096.ebotcazou@libertysurf.fr> X-SW-Source: 2003-02/txt/msg00627.txt.bz2 > Given that this seems to be consensus (with Gaby, Geoff,...) using and/or > preferring it as well, would (one of) you volunteer to submit this as a > suggestion for > > http://www.gnu.org/prep/standards_toc.html > > or our codingconventions.html? Something like this: Index: codingconventions.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v retrieving revision 1.18 diff -u -r1.18 codingconventions.html --- codingconventions.html 7 Dec 2002 13:51:44 -0000 1.18 +++ codingconventions.html 11 Feb 2003 10:14:49 -0000 @@ -56,7 +56,11 @@ particular, descriptions of the purpose of code and changes should go in comments rather than the ChangeLog, though a single line overall description of the changes may be useful above the ChangeLog entry for -a large batch of changes.

+a large batch of changes. For changes that are backported from another +branch to the working one, we recommend to use a single entry whose +body contains a verbatim copy of the whole (header+body) entries +describing the changes on the source branch, possibly preceded by a +single line overall description of the changes.

There is no established convention on when ChangeLog entries are to be made for testsuite changes; see messages