From: Jeffrey A Law <law@cygnus.com>
To: Jim Wilson <wilson@cygnus.com>
Cc: egcs@cygnus.com, Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
Subject: Re: Changelog time format
Date: Sun, 17 May 1998 22:03:00 -0000 [thread overview]
Message-ID: <11282.895450897@hurl.cygnus.com> (raw)
In-Reply-To: <199805172212.PAA04043@rtl.cygnus.com>
In message < 199805172212.PAA04043@rtl.cygnus.com >you write:
> I noticed that this was installed, but it doesn't seem to do anything usefu l.
It's of marginal value (IMHO). But I didn't see a signifcant
reason not to install the change.
If folks object, we can always pull it out.
> Simply adding it to one of the ChangeLog files in gcc isn't interesting.
> We either add it to all of them or none of them.
Well, 99% of our changes go into gcc/ChangeLog and gcc/cp/ChangeLog
And (IMHO) we probably don't want to go adding this to things like
texinfo, libio, libstdc++ which are maintained externally.
> We can't add it to all
> of them unless we get everyone to agree that the old format is better.
I don't think we need to get everyone to agree. We can't please
everyone, so we shouldn't try
> Also, the change isn't going to force all ChangeLog entries to use the
> new format. I always create a patch file, add the ChangeLog entry to the
> patch file, and then copy it into the ChangeLog file. Hence all of the
> patches I create on my Linux machine will continue to use the new format.
Absolutely. I actually make my ChangeLog entries with a vi macro,
jeff
next prev parent reply other threads:[~1998-05-17 22:03 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 [this message]
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
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=11282.895450897@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=martin@mira.isdn.cs.tu-berlin.de \
--cc=wilson@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).