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 21:22:35 +0100 Organization: Linux Private Site Message-ID: <87wqif7b04.fsf@Rainer.invalid> References: <20140102095347.6834E381D0C@snark.thyrsus.com> <87fvp6bdd9.fsf_-_@ktab.red-bean.com> <8761q1ljny.fsf@gmail.com> <20140103175006.GE17261@thyrsus.com> <87iou0t72n.fsf@bzg.ath.cx> <87a9fb99qg.fsf@Rainer.invalid> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1388866993 17680 80.91.229.3 (4 Jan 2014 20:23:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jan 2014 20:23:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 04 21:23:19 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 1VzXkb-0006fd-Uo for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2014 21:23:18 +0100 Original-Received: from localhost ([::1]:55652 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzXkb-0003X8-GB for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2014 15:23:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54320) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzXkQ-0003Wz-IS for emacs-devel@gnu.org; Sat, 04 Jan 2014 15:23:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VzXkJ-0006Br-24 for emacs-devel@gnu.org; Sat, 04 Jan 2014 15:23:06 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:35063) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzXkI-0006Bf-S4 for emacs-devel@gnu.org; Sat, 04 Jan 2014 15:22:58 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VzXkG-00061Q-GA for emacs-devel@gnu.org; Sat, 04 Jan 2014 21:22:56 +0100 Original-Received: from pd9eb013b.dip0.t-ipconnect.de ([217.235.1.59]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 Jan 2014 21:22:56 +0100 Original-Received: from Stromeko by pd9eb013b.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 Jan 2014 21:22:56 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pd9eb013b.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:Mu/jI6EQeSTfPJslVZ/MLwZze9g= 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:167323 Archived-At: Stefan Monnier writes: >> be) identical, then manually entering the same information in two >> different places is unnecessarily complex and error-prone, so generating > > If you enter it twice, you're not using your tool right. Emacs can > extract the commit message from the ChangeLog file right before you > commit, so you don't have to enter it twice. That's exactly what I said in the next line of that sentence which you didn't quote. I purposefully avoided the contentious issue of saying which direction I might prefer. > The main issues were (and are) the following: > - How to edit past commit messages when they're > incorrect/incomplete/...? Git notes still seems like a good solution. > - How to do C-x 4 a when there's no ChangeLog file? You don't need to. I'm usually writing the commit messages as I stage the diffs for the upcoming commit. I also frequently rewrite commits before pushing them upstream. Extracting that information from a ChangeLog to build the commit message is completely backwards with that kind of workflow and easily leads to typical errors like documenting changes that aren't actually committed or implemented differently or additional undocumented changes that might or might not be intended to be part of the commit. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds