unofficial mirror of emacs-devel@gnu.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 10:33:41 +0200	[thread overview]
Message-ID: <83lhmvn2qi.fsf@gnu.org> (raw)
In-Reply-To: <87a93c5fgt.fsf@lifelogs.com>

> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Thu, 27 Nov 2014 19:36:02 -0500
> 
> On Thu, 27 Nov 2014 18:12:13 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 
> 
> >> Date: Thu, 27 Nov 2014 08:34:00 +0100
> >> From: Ulrich Mueller <ulm@gentoo.org>
> >> 
> >> When merging commits or applying a patch, should the date in the
> >> ChangeLog be left alone, or updated to the current date? In other
> >> words, should the ChangeLog date be equal to git's AuthorDate (in
> >> which case dates can be out of sequence) or CommitDate?
> 
> 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.

Of course; even I know that.  But the script that generates ChangeLog
from the commit log could modify the dates, if we decide that to be
TRT.



  reply	other threads:[~2014-11-28  8:33 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 [this message]
2014-11-28 11:02       ` Ted Zlatanov
2014-11-28 11:06         ` Eli Zaretskii
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

  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=83lhmvn2qi.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 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).