From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22173 invoked by alias); 19 May 2003 15:06:35 -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 22162 invoked from network); 19 May 2003 15:06:35 -0000 Received: from unknown (HELO catalunya) (134.217.237.30) by sources.redhat.com with SMTP; 19 May 2003 15:06:35 -0000 Received: from kraai by catalunya with local (Exim 3.35 #1 (Debian)) id 19HmDR-00040U-00; Mon, 19 May 2003 08:06:17 -0700 Date: Mon, 19 May 2003 15:07:00 -0000 From: Matt Kraai To: Gerald Pfeifer Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: "obvious" requirements Message-ID: <20030519150617.GB13692@ftbfs.org> Mail-Followup-To: Gerald Pfeifer , gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org References: <20030518232511.GE13668@ftbfs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-SW-Source: 2003-05/txt/msg01762.txt.bz2 On Mon, May 19, 2003 at 11:20:00AM +0200, Gerald Pfeifer wrote: > On Sun, 18 May 2003, Matt Kraai wrote: > > I'd like to make a obvious fix to tree.c (i.e., remove a blank > > line). Should I add an entry to the ChangeLog and/or post the > > patch to gcc-patches? > > ChangeLog? Dunno about such a corner case. So ChangeLog entries are sometimes required... > gcc-patches? Definitely, though it's fine after the fact for obvious > changes. ...and postings to gcc-patches are always required. OK to commit the following? -- Matt Kraai Debian GNU/Linux Peon *** cvswrite.html.~1.52.~ Wed Mar 26 13:18:35 2003 --- cvswrite.html Mon May 19 08:05:30 2003 *************** *** 135,142 ****

Also note that fixes for obvious typos in ChangeLog files, docs, web pages, comments and similar stuff need not be approved. Just ! check in the fix. We don't want to get overly anal about checkin ! policies.

When you have checked in a patch exactly as it has been approved, you do not need to tell that to people -- including the approver. --- 135,142 ----

Also note that fixes for obvious typos in ChangeLog files, docs, web pages, comments and similar stuff need not be approved. Just ! check in the fix and copy it to gcc-patches. We don't ! want to get overly anal about checkin policies.

When you have checked in a patch exactly as it has been approved, you do not need to tell that to people -- including the approver.