all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 20717@debbugs.gnu.org
Subject: bug#20717: attribution of gitmerge.el merged entries in generated	ChangeLog
Date: Thu, 11 Jun 2015 05:46:19 +0300	[thread overview]
Message-ID: <83r3pjrmh0.fsf@gnu.org> (raw)
In-Reply-To: <6ovbevf2zb.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Cc: 20717@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?





  parent reply	other threads:[~2015-06-11  2:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02  6:22 bug#20717: attribution of gitmerge.el merged entries in generated ChangeLog Glenn Morris
2015-06-05 22:06 ` Glenn Morris
2015-06-06  6:55   ` Eli Zaretskii
2015-06-06 18:13     ` Glenn Morris
2015-06-06 18:48       ` Glenn Morris
2015-06-06 19:32         ` Eli Zaretskii
2015-06-11  1:28           ` Glenn Morris
2015-06-11  1:41             ` Glenn Morris
2017-12-23  2:57               ` Glenn Morris
2015-06-11  2:46             ` Eli Zaretskii [this message]
2015-06-08 13:52     ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r3pjrmh0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20717@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.