From: Jim Wilson <wilson@cygnus.com>
To: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
Cc: law@cygnus.com, egcs@cygnus.com,
Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
Subject: Re: Changelog time format
Date: Mon, 18 May 1998 15:38:00 -0000 [thread overview]
Message-ID: <199805181944.MAA05755@rtl.cygnus.com> (raw)
In-Reply-To: <vyzwwbkq6q7.fsf@issan.informatik.uni-dortmund.de>
IMHO the best solution would be to install a wrapper in CVS that converts
the time stamps to the old format on checkin. The only problem is that
the new format lacks timeofday information.
I like to think of that as a feature. I find it annoying that the current
formats have timeofday info, but do not include timezone info, and hence
they can be misleading. If you really need timeofday info, get it from
the CVS logs.
The timeofday info is also inaccurate because there is often little
correlation between the time of the changelog entry and the time that
the patch is actually checked in.
I think the best solution is to simply accept the fact that there are two
formats for ChangeLog entries, and that the new format will prevail over
time because the FSF has adopted it as the standard (i.e. default) format.
If you want to argue the issue, then argue it with the FSF. EGCS should
just be following the FSF style guidelines, not creating our own.
Jim
next prev parent reply other threads:[~1998-05-18 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-09 6:51 Martin von Loewis
1998-05-09 23:32 ` Jeffrey A Law
1998-05-10 2:05 ` Martin von Loewis
1998-05-17 17:58 ` Jim Wilson
1998-05-17 22:03 ` Jeffrey A Law
1998-05-18 6:02 ` Franz Sirl
1998-05-18 6:02 ` Andreas Schwab
1998-05-18 15:38 ` Jim Wilson [this message]
1998-05-18 15:38 ` Martin von Loewis
[not found] ` <199805181944.MAA05755.cygnus.egcs@rtl.cygnus.com>
1998-05-18 23:58 ` Ulrich Drepper
1998-05-20 1:45 ` Jim Wilson
1998-05-20 2:27 ` Ulrich Drepper
1998-05-20 19:03 ` Jim Wilson
1998-05-20 19:03 ` Ulrich Drepper
1998-05-20 9:26 ` Dave Love
1998-05-19 15:59 Mike Stump
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=199805181944.MAA05755@rtl.cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=martin@mira.isdn.cs.tu-berlin.de \
--cc=schwab@issan.informatik.uni-dortmund.de \
/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.
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).