unofficial mirror of bug-gnu-emacs@gnu.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: Sat, 06 Jun 2015 22:32:04 +0300	[thread overview]
Message-ID: <83lhfwmy4r.fsf@gnu.org> (raw)
In-Reply-To: <wqpp58ekq0.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Cc: 20717@debbugs.gnu.org
> Date: Sat, 06 Jun 2015 14:48:55 -0400
> 
> 1. The dates of merged entries are wrong by an arbitrary amount.
> You can see the "cairo" entries in current ChangeLog.2 for an example of
> this. IIUC, this isn't fixable without getting the reflog involved.
> Ref: http://lists.gnu.org/archive/html/emacs-devel/2014-12/msg00102.html
> 
> 2. Entries that were "skipped" when gitmerge.el'ing from emacs-24 to
> master still appear in the generated ChangeLog. Check tomorrow's
> automatically updated ChangeLog.2 for examples of that. Or type `make
> ChangeLog' today. You'll see entries like
> 
> 2015-04-11  Ulrich Mueller <ulm>
> 
>        Bump Emacs version to 24.5.50.
> 
> that were skipped when merging from emacs-24. It's especially confusing
> because if merging isn't done very often (and recent history suggests it
> won't be), these entries will be offset from the relevant "Merge from
> origin/emacs-24" entry by a large distance. This isn't an issue now
> because the emacs-24 branch is basically dead, but it will be for the
> next release.

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?  They shouldn't appear at all, I
think.

> I would hope that this one is fixable, with some work on admin/gitmerge.el
> and/or build-aux/gitlog-to-changelog.

I hope so too.

> But I get the impression that a readable ChangeLog isn't much of a
> priority for Emacs anymore. Maybe no-one will miss it.

I will.





  reply	other threads:[~2015-06-06 19:32 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83lhfwmy4r.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).