all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: ChangeLog dates
Date: Fri, 28 Nov 2014 14:52:40 -0500	[thread overview]
Message-ID: <87wq6f2jcn.fsf@lifelogs.com> (raw)
In-Reply-To: 83bnnrmncc.fsf@gnu.org

On Fri, 28 Nov 2014 16:06:11 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 

>> From: Ted Zlatanov <tzz@lifelogs.com>
>> Date: Fri, 28 Nov 2014 08:57:41 -0500
>> 
EZ> Seen from the master's POV, keeping the dates from the original
EZ> (branch) commits would be rewriting history, because the actual date
EZ> the commits appeared on master are different.
>> 
>> But the commit's date is "baked" into it by Git. So there's no "master"
>> POV for commit dates, only for when the commits are accessible via
>> "master" (and both dates are relevant, hence I suggested adding a note).

EZ> I'm not talking about Git's history, or accessing history through Git.
EZ> I'm talking about ChangeLog files looked at by people who have only
EZ> the release tarball (which is why we produce ChangeLog files).  They
EZ> don't have Git, they have just the ChangeLog files, and those
EZ> ChangeLog files should IMO reflect the ordered sequence of commits to
EZ> the branch from which the tarball was created.

I understand. I personally would be OK with either the original dates
with a side note, or the adjusted dates in such a packaged ChangeLog.

Thanks for explaining
Ted




  reply	other threads:[~2014-11-28 19:52 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
2014-11-28 13:57           ` Ted Zlatanov
2014-11-28 14:06             ` Eli Zaretskii
2014-11-28 19:52               ` Ted Zlatanov [this message]
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=87wq6f2jcn.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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.