GNU bug report logs - #20717
date of generated ChangeLog entries for (git)merged commits

Previous Next

Full log

Message #40 received at 20717 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 20717 <at> debbugs.gnu.org
Subject: Re: bug#20717: attribution of gitmerge.el merged entries in
 generated	ChangeLog
Date: Thu, 11 Jun 2015 05:46:19 +0300

> From: Glenn Morris <rgm <at> gnu.org>
> Cc: 20717 <at> debbugs.gnu.org
> Date: Wed, 10 Jun 2015 21:28:08 -0400
> 
> Eli Zaretskii wrote:
> 
> > Do logs of changes made on feature branches also appear like that, and
> > are also misplaced?  E.g., what do you get there of the commits on the
> > large-fonts branch I merged today?
> 
> See
> http://lists.gnu.org/archive/html/emacs-diffs/2015-06/msg00090.html
> 
> The word "merge" isn't even mentioned in gitlog-to-changelog, and it's 7
> years old, so I assume no-one cares about such things. Frankly, it's not
> much more than a dump of "git log" with some formatting tweaks to make
> it look more like a ChangeLog.

So should we manually correct the most glaring problems of the result
of this?  For example, the logs for commits I made on that branch
should be deleted, as there's a summary log for the merge-commit later
on that covers them all.

Perhaps we should recommend that people use the ";" trick in the log
messages they make on branches they intend to merge onto master later?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.