all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: ChangeLog dates
Date: Fri, 28 Nov 2014 13:06:54 +0200	[thread overview]
Message-ID: <83d287mvn5.fsf@gnu.org> (raw)
In-Reply-To: <87oarr4mg9.fsf@lifelogs.com>

> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Fri, 28 Nov 2014 06:02:46 -0500
> 
> On Fri, 28 Nov 2014 10:33:41 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 
> 
> EZ> Until now we did the latter, i.e. updated the entry's date to the date
> EZ> of the merge.  I don't know what's TRT when ChangeLog's will be
> EZ> generated.
> >> 
> >> It's going to have to be the original date, because AFAIK it's part of
> >> the commit hash.
> 
> EZ> Of course; even I know that.
> 
> I didn't before I checked :)
> 
> EZ> But the script that generates ChangeLog from the commit log could
> EZ> modify the dates, if we decide that to be TRT.
> 
> It will be painful and I think faking the date was an artifact of the
> static ChangeLog system rather than actually needed. It would probably
> be better to preserve the original commit date in the auto-generated
> ChangeLog but add a note that the commit was merged/backported to branch
> X on date Y.

Seen from the master's POV, keeping the dates from the original
(branch) commits would be rewriting history, because the actual date
the commits appeared on master are different.



  reply	other threads:[~2014-11-28 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  7:34 ChangeLog dates Ulrich Mueller
2014-11-27 16:12 ` Eli Zaretskii
2014-11-28  0:36   ` Ted Zlatanov
2014-11-28  8:33     ` Eli Zaretskii
2014-11-28 11:02       ` Ted Zlatanov
2014-11-28 11:06         ` Eli Zaretskii [this message]
2014-11-28 13:57           ` Ted Zlatanov
2014-11-28 14:06             ` Eli Zaretskii
2014-11-28 19:52               ` Ted Zlatanov
2014-11-29 20:02               ` Glenn Morris

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=83d287mvn5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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.