From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Kastrup <dak@gnu.org>
Cc: Vinicius Jose Latorre <viniciusjl@ig.com.br>, emacs-devel@gnu.org
Subject: Re: ChangeLog entry timestamp
Date: Fri, 03 Aug 2007 10:52:18 -0400 [thread overview]
Message-ID: <jwvk5scwu29.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86ejikit99.fsf@lola.quinscape.zz> (David Kastrup's message of "Fri\, 03 Aug 2007 16\:32\:02 +0200")
>> I've just noticed that entries timestamp in ChangeLog (trunk and Emacs
>> 22 branch) are unsorted, that is, there are entries as:
>>
>> 2007-08-03 ...
>> 2007-08-02 ...
>> 2007-07-31 ... <<<
>> 2007-08-03 ... <<<
>> 2007-08-01 ...
>> 2007-07-31 ...
>> 2007-07-29 ...
>> 2007-07-28 ...
>> 2007-07-30 ... <<<
>> 2007-07-29 ... <<<
>> 2007-07-28 ...
>> 2007-07-27 ...
>> 2007-07-26 ...
>> 2007-07-25 ...
>> 2007-07-24 ...
>> 2007-07-25 ... <<<
>> 2007-07-24 ...
>> 2007-07-23 ...
>> 2007-07-20 ... <<<
>> 2007-07-23 ...
>> 2007-07-22 ...
>> etc.
>>
>> Is this a problem? Should the entries be sorted?
> No. The dates are when the patches have been created, the order is
> according to when they have been committed.
Actually, the date should be the date it was committed, so it should
be sorted. Not sure about what should happen in case of merges, tho.
> Even if people would always commit immediately, we would not get calendar
> linearity because of differing timezones.
We've switched to UTC times some months (year?) ago, so this shouldn't be an
issue any more.
Stefan
next prev parent reply other threads:[~2007-08-03 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 14:22 ChangeLog entry timestamp Vinicius Jose Latorre
2007-08-03 14:32 ` David Kastrup
2007-08-03 14:52 ` Stefan Monnier [this message]
2007-08-03 14:54 ` David Kastrup
2007-08-03 15:47 ` Andreas Schwab
2007-08-03 15:55 ` Jason Rumney
2007-08-03 22:01 ` Richard Stallman
2007-08-03 15:51 ` Miles Bader
2007-08-03 22:01 ` Richard Stallman
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=jwvk5scwu29.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=viniciusjl@ig.com.br \
/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.