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: Is it time to drop ChangeLogs? Date: Fri, 11 Mar 2016 10:48:13 +0200 Message-ID: <83wpp9jt82.fsf@gnu.org> References: <56BE7E37.3090708@cs.ucla.edu> <4hd1rw1ubr.fsf@fencepost.gnu.org> <83vb50wxhv.fsf@gnu.org> <87y49vz4cg.fsf@acer.localhost.com> <64a52598-ad53-498c-993c-67d7827dbdfc@default> <838u1uuuau.fsf@gnu.org> <878u1um2xl.fsf@thinkpad.rath.org> <87fuw090k7.fsf@wanadoo.es> <83y49spuxt.fsf@gnu.org> <87pov4achc.fsf@acer.localhost.com> <83r3fkpb3u.fsf@gnu.org> <83lh5rps0t.fsf@gnu.org> <56E066BD.5050403@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1457686128 30171 80.91.229.3 (11 Mar 2016 08:48:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 11 Mar 2016 08:48:48 +0000 (UTC) Cc: eggert@cs.ucla.edu, johnw@gnu.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 11 09:48:43 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 1aeIkU-0005lC-Tg for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2016 09:48:43 +0100 Original-Received: from localhost ([::1]:53428 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeIkU-0001zt-4l for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2016 03:48:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58233) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeIkR-0001zd-8b for emacs-devel@gnu.org; Fri, 11 Mar 2016 03:48:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aeIkQ-00041Q-Eu for emacs-devel@gnu.org; Fri, 11 Mar 2016 03:48:39 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57127) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeIkK-00040e-Rx; Fri, 11 Mar 2016 03:48:32 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3250 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aeIk6-00030z-A1; Fri, 11 Mar 2016 03:48:19 -0500 In-reply-to: (message from Richard Stallman on Thu, 10 Mar 2016 16:23:48 -0500) 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:201451 Archived-At: > From: Richard Stallman > CC: eliz@gnu.org, johnw@gnu.org, emacs-devel@gnu.org > Date: Thu, 10 Mar 2016 16:23:48 -0500 > > Even though Git does not permit editing a commit message _as such_, we > can provide, at a higher level, a way to correct old commit messages. > Maintaining a ChangeLog file in the repository is one way to do this, > but if it has flaws in the case of merging, can we design another mechanism > for the job that solves the problems with merging? The known mechanisms are user-unfriendly, in that they require to write the corrections as editing commands for Perl or some other Sed-like facility. This is too error prone for a feature that should be usable by non-experts. A facility that could be considered is one that allows to type the correction as plain text which should replace the existing text in the Git log. We haven't found such a facility yet. "git replace" sounds like a promising alternative, though.