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 1O1isb-00086W-LT for garchives@archives.gentoo.org; Tue, 13 Apr 2010 16:22:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A0F48E0825; Tue, 13 Apr 2010 16:22:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 1F419E0817 for ; Tue, 13 Apr 2010 16:22:19 +0000 (UTC) Received: from [10.0.2.10] (unknown [81.193.95.189]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 278841B40D9 for ; Tue, 13 Apr 2010 16:22:17 +0000 (UTC) Message-ID: <4BC49A35.60900@gentoo.org> Date: Tue, 13 Apr 2010 18:22:13 +0200 From: Angelo Arrifano Organization: Gentoo Linux Foundation User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100317 Lightning/1.0b2pre Thunderbird/3.0.3 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [git migration] The problem of ChangeLog generation References: <1271157930.11850.977.camel@tablet> <19396.28532.913516.120152@a1i15.kph.uni-mainz.de> <4BC497F0.9080606@gentoo.org> In-Reply-To: <4BC497F0.9080606@gentoo.org> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 0a0d147a-5a2e-460e-94f8-d0718a1937e8 X-Archives-Hash: 2fca4c8d3ab1d2e16ace833966f6b624 On 13-04-2010 18:12, Matti Bickel wrote: > Nirbheek Chauhan wrote: >> From my PoV, editing ChangeLog is like editing history. Complete no-no. > > It is possible in all major SCMs for a reason. And I (as a user) would > laugh at Changelog entries saying "um, I got that bug number wrong, it > is really #1234". If I (as a developer) log such edits, I'm wasting my > users time. > > So I'll continue to edit and commit Changelogs without additional notice. > Can't we just create a commit hook that appends the bug summary as a comment if a #XXXXX bug string is present on the commit log? Something like: - - Foobar commit Description bl a bla bla # bug 1234: Show summary for those that don't double check the bug # number. # # Other git crap that usually appears at end of log # ... - -