From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Should we restore manually maintained ChangeLogs Date: Thu, 10 Mar 2016 15:08:39 +0200 Message-ID: <831t7imqeg.fsf@gnu.org> References: <83lh5utbxb.fsf@gnu.org> <56DDD02A.20809@cs.ucla.edu> <83fuw2t2ue.fsf@gnu.org> <56DE0F6A.6010207@cs.ucla.edu> <83pov5rmt6.fsf@gnu.org> <56DFD78F.40205@cs.ucla.edu> <56E06093.7050509@cs.ucla.edu> <83twkfo7ij.fsf@gnu.org> <20160309181005.GF3948@acm.fritz.box> <87vb4vuu59.fsf@thinkpad.rath.org> <87pov3nrnm.fsf@linux-m68k.org> <83mvq6n7xs.fsf@gnu.org> <83d1r2mzuy.fsf@gnu.org> <8360wumxj4.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1457615340 12434 80.91.229.3 (10 Mar 2016 13:09:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Mar 2016 13:09:00 +0000 (UTC) Cc: schwab@linux-m68k.org, emacs-devel@gnu.org To: Sven Axelsson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 10 14:08:55 2016 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 1ae0Ke-000390-SA for ged-emacs-devel@m.gmane.org; Thu, 10 Mar 2016 14:08:49 +0100 Original-Received: from localhost ([::1]:48297 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ae0Ke-00061t-54 for ged-emacs-devel@m.gmane.org; Thu, 10 Mar 2016 08:08:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ae0KK-00060v-Fq for emacs-devel@gnu.org; Thu, 10 Mar 2016 08:08:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ae0KH-0002sB-91 for emacs-devel@gnu.org; Thu, 10 Mar 2016 08:08:28 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41499) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ae0KH-0002s7-5K; Thu, 10 Mar 2016 08:08:25 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1346 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ae0KG-00081n-Dp; Thu, 10 Mar 2016 08:08:24 -0500 In-reply-to: (message from Sven Axelsson on Thu, 10 Mar 2016 12:49:34 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:201378 Archived-At: > Date: Thu, 10 Mar 2016 12:49:34 +0100 > From: Sven Axelsson > Cc: Andreas Schwab , emacs > > When you only want to deal with changing the commit message and not > the actual commit, it is as simple as calling `git replace --edit > '. This will bring up your system editor where you can change the > commit message. > > Doing it this way will not change history. How can it not change history, when (AFAIK) the log message is part of the commit object, and it included in the stuff that determines the SHA1 checksum of the commit?