From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req. Date: Sat, 04 Jan 2014 14:15:25 +0100 Organization: Linux Private Site Message-ID: <8761pz99ci.fsf@Rainer.invalid> References: <20140102095347.6834E381D0C@snark.thyrsus.com> <87fvp6bdd9.fsf_-_@ktab.red-bean.com> <8761q1ljny.fsf@gmail.com> <87lhyxqztz.fsf@gmx.de> <87mwjct755.fsf@bzg.ath.cx> <87eh4n9ak6.fsf@Rainer.invalid> <87d2k7x5sl.fsf@bzg.ath.cx> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1388841354 19778 80.91.229.3 (4 Jan 2014 13:15:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jan 2014 13:15:54 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 04 14:16:00 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VzR55-00011f-Vy for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2014 14:16:00 +0100 Original-Received: from localhost ([::1]:54439 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzR55-0000LY-IU for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2014 08:15:59 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38555) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzR4t-00005c-FZ for emacs-devel@gnu.org; Sat, 04 Jan 2014 08:15:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VzR4n-00023k-AO for emacs-devel@gnu.org; Sat, 04 Jan 2014 08:15:47 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:50113) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzR4n-00023g-3P for emacs-devel@gnu.org; Sat, 04 Jan 2014 08:15:41 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VzR4m-0000RZ-FI for emacs-devel@gnu.org; Sat, 04 Jan 2014 14:15:40 +0100 Original-Received: from pd9eb2345.dip0.t-ipconnect.de ([217.235.35.69]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 Jan 2014 14:15:40 +0100 Original-Received: from Stromeko by pd9eb2345.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 Jan 2014 14:15:40 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 39 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pd9eb2345.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:x06glW2kaAORv/Q1OGGHjUyCIck= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:167285 Archived-At: Bastien writes: > My question is: if Emacs generates Changelogs from commit messages, > and if commit messages contain ill-formated changelogs, how do you > fix generated changelogs? If you've got a version-controlled ChangeLog file (status quo), it is completely immaterial of how the entries are produced. Even if they are all generated, you can still edit the file, just as you've done all the time. > One idea is to generate only new changes (and fix them manually if > needed), not to generate all ChangeLogs. Generating all ChangeLogs is superfluous since then you don't need a ChangeLog at all. > It's a matter of convention: if Emacs generates Changelog files from > commit messages, I guess we will enforce some policy on how to write > suitable commit messages. Again, this is an argument to abolish ChangeLogs altogether. > Additional (not suitable for ChangeLogs) information could then be > stored in git notes. Git notes are simply a way to augment or correct the original commit message (which can't be separated from the commit without rewriting history). As such it should be used sparingly, if at all. I'd rather have code review that ensures the commit messages are good than git notes. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada