From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QR1WR-0007B6-4r for garchives@archives.gentoo.org; Mon, 30 May 2011 12:24:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B0CA21C11A; Mon, 30 May 2011 12:24:29 +0000 (UTC) Received: from a1iwww1.kph.uni-mainz.de (a1iwww1.kph.uni-mainz.de [134.93.134.1]) by pigeon.gentoo.org (Postfix) with ESMTP id C72651C102 for ; Mon, 30 May 2011 12:23:11 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92]) by a1iwww1.kph.uni-mainz.de (8.14.4/8.13.4) with ESMTP id p4UCNAYx015626 for ; Mon, 30 May 2011 14:23:10 +0200 Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1]) by a1i15.kph.uni-mainz.de (8.14.4/8.14.2) with ESMTP id p4UCNA6J012766; Mon, 30 May 2011 14:23:10 +0200 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.4/8.14.4/Submit) id p4UCNADU012765; Mon, 30 May 2011 14:23:10 +0200 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19939.35885.986402.435154@a1i15.kph.uni-mainz.de> Date: Mon, 30 May 2011 14:23:09 +0200 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Council May Summary: Changes to ChangeLog handling In-Reply-To: <1306757022.9216.36.camel@tablet> References: <4DD24EBE.5060002@gentoo.org> <1305886782.17955.29.camel@localhost> <1306757022.9216.36.camel@tablet> X-Mailer: VM 8.1.1 under 23.3.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller X-Archives-Salt: X-Archives-Hash: e9b5995d10ee063f0bea82cefc06bc89 >>>>> On Mon, 30 May 2011, Peter Volkov wrote: > So, I just realized that we have to update Changelogs for > everything, whitespaces and comments included. Even after reading > meeting logs I still wonder, why council have decided to vote policy > change that was not supported even by minority of developers? The > whole idea after human editable ChangeLogs was to avoid whitespace > changes and changes in comments. In the current state it is possible > to generate them on rsync servers and avoid this burden. > I would like council to update policy to allow exclude whitespace > changes and changes in comments. I second this. The council should also clarify how to treat the ChangeLog in case of package removals. The devmanual requires that it is updated even in this case, whereas the handbook says that all files should be removed. Ulrich