From: Jim Wilson <wilson@cygnus.com>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: egcs@cygnus.com
Subject: Re: Changelog time format
Date: Wed, 20 May 1998 01:45:00 -0000 [thread overview]
Message-ID: <199805200340.UAA12634@rtl.cygnus.com> (raw)
In-Reply-To: <r2hg2mx1dj.fsf@happy.cygnus.com>
Many GNU packages (tar, recode, gettext, glibc, sharutils, patch,
fileutils, grep) are already using the ISO 8601 format and for many
others it's simply a matter of getting out a new version. gcc/egcs
are again one of the last packages to convert to this format.
I think you are ignoring the fact that gcc/egcs are fundamentally different
than the other packages you mentioned. Compare how many people have write
access to glibc versus how many people have write access to egcs. The more
people are involved, the longer it takes to make process changes. It only
took one person to decide that glibc should switch to the new format. It
will take 10 or so for egcs to decide to switch to the new format. That
is why egcs is inevitably lagging behind.
It would actually help egcs if the ChangeLog format was explicitly written
into the FSF style guides. Then at least my arguments in favor of the
new format would be more convincing.
Jim
next prev parent reply other threads:[~1998-05-20 1:45 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
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 [this message]
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=199805200340.UAA12634@rtl.cygnus.com \
--to=wilson@cygnus.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
/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).