From: Marc Espie <espie@quatramaran.ens.fr>
To: gcc@gcc.gnu.org
Subject: Re: Conerned about lack of detail in ChangeLog/commit messges
Date: Sun, 11 Jun 2000 06:38:00 -0000 [thread overview]
Message-ID: <200006111338.PAA26714@quatramaran.ens.fr> (raw)
In-Reply-To: <m34s723ka3.fsf@nick.ws.noc.dsvr.net>
Yeah, gcc doesn't make a sensible utilisation of cvs, does it ?
At least it's somewhat different from most other projects that use it
that I know.
The proposal of generating the cvs logs from the Changelog is somewhat
backwards. It would probably be much, much simpler to generate a ChangeLog
out of cvs commit messages. In fact, this is how other projects usually
do it. Cvs does yield fairly nice commit messages. That would solve
one specific problem: all files changed would be automatically mentioned
in the commit message. The format can be tweaked afterwards to be as
compliant with the Changelog entry as one wishes...
In fact, I would very much prefer having the Changelog match the committed
date, not some other somewhat artificial dates. There are lots of other ways
to refer to a patch, the entry in the gcc-patches archive comes to mind.
And David is quite correct that using the ChangeLog to browse through the
history of one file is a pain... One loses most of the features that make
cvs useful. For instance, `cvs annotate' is almost useless on gcc,
since it is very hard to go back from gcc revisions to Changelog entry.
I understand that this is somewhat hard to change, but consider it.
There might be a good reason why other projects are actually USING cvs for
day-to-day work, might there not ? :)
next prev parent reply other threads:[~2000-06-11 6:38 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 12:42 David O'Brien
2000-06-08 15:18 ` Martin v. Loewis
2000-06-09 8:30 ` David Edelsohn
2000-06-09 8:51 ` David O'Brien
2000-06-09 9:13 ` Nick Burrett
2000-06-09 9:21 ` David O'Brien
2000-06-11 6:38 ` Marc Espie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 18:21 [PATCH] rs6000.c ELF bits inclusion David O'Brien
2001-05-02 20:07 ` David Edelsohn
2001-05-02 20:32 ` David O'Brien
2001-05-02 20:52 ` David Edelsohn
2001-05-03 0:39 ` David O'Brien
2001-05-03 13:17 ` David O'Brien
2001-05-03 16:04 ` David Edelsohn
2001-05-03 19:11 ` David O'Brien
2000-06-18 14:10 Conerned about lack of detail in ChangeLog/commit messges Richard Kenner
2000-06-18 12:32 Mike Stump
2000-06-18 11:32 Richard Kenner
2000-06-17 8:41 Richard Kenner
2000-06-18 8:05 ` Martin v. Loewis
1999-09-14 19:32 FreeBSD 4.0 Wes Morgan
1999-09-14 20:08 ` Richard Henderson
1999-09-15 2:00 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Richard Henderson
1999-09-14 22:34 ` Loren James Rittle
1999-09-14 23:00 ` Zack Weinberg
1999-09-14 23:14 ` David O'Brien
1999-09-15 0:25 ` Zack Weinberg
1999-09-15 0:56 ` David O'Brien
1999-09-15 1:21 ` Andreas Schwab
1999-09-15 1:40 ` David O'Brien
1999-09-15 2:23 ` Andreas Schwab
1999-09-15 3:11 ` David O'Brien
1999-09-15 3:52 ` Andreas Schwab
1999-09-30 18:02 ` Andreas Schwab
1999-09-30 18:02 ` David O'Brien
1999-09-30 18:02 ` Andreas Schwab
1999-09-20 3:58 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` David O'Brien
1999-09-30 18:02 ` Andreas Schwab
1999-09-30 18:02 ` David O'Brien
1999-09-15 1:17 ` David O'Brien
1999-09-15 9:23 ` Zack Weinberg
1999-09-15 10:24 ` David O'Brien
1999-09-16 14:48 ` Richard Henderson
1999-09-30 18:02 ` Richard Henderson
1999-09-30 18:02 ` David O'Brien
1999-09-20 4:20 ` Jeffrey A Law
1999-09-21 6:33 ` The USER_H issue Marc Espie
1999-09-30 18:02 ` Marc Espie
1999-09-30 18:02 ` FreeBSD 4.0 Jeffrey A Law
1999-09-30 18:02 ` Zack Weinberg
1999-09-20 4:34 ` Jeffrey A Law
1999-09-20 9:26 ` Zack Weinberg
1999-09-20 9:55 ` Jeffrey A Law
1999-09-20 10:17 ` Zack Weinberg
1999-09-20 10:38 ` Richard Earnshaw
1999-09-20 11:02 ` Zack Weinberg
1999-09-30 18:02 ` Zack Weinberg
1999-09-20 11:39 ` Horst von Brand
1999-09-20 11:49 ` Chris G. Demetriou
1999-09-30 18:02 ` Chris G. Demetriou
1999-09-30 18:02 ` Horst von Brand
1999-09-30 18:02 ` Richard Earnshaw
1999-09-23 8:51 ` Jeffrey A Law
1999-09-23 9:13 ` Pending Projects Bruce Korb
1999-09-30 18:02 ` Bruce Korb
1999-09-30 18:02 ` FreeBSD 4.0 Jeffrey A Law
1999-09-30 18:02 ` Zack Weinberg
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Zack Weinberg
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` David O'Brien
1999-09-30 18:02 ` Zack Weinberg
1999-09-15 2:00 ` Jeffrey A Law
1999-09-15 2:25 ` David O'Brien
1999-09-15 2:33 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` David O'Brien
[not found] ` <37DFAD27.3E6A25E3@datadesign.com>
[not found] ` <199909152042.PAA29374@latour.rsch.comm.mot.com>
1999-09-15 14:26 ` Bruce Korb
1999-09-15 17:10 ` Jeffrey A Law
1999-09-16 1:46 ` Marc Espie
1999-09-16 6:57 ` Jeffrey A Law
1999-09-16 7:41 ` Marc Espie
1999-09-16 7:55 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Marc Espie
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Marc Espie
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Bruce Korb
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` David O'Brien
1999-09-15 1:59 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Zack Weinberg
1999-09-15 7:42 ` Wes Morgan
1999-09-30 18:02 ` Wes Morgan
1999-09-30 18:02 ` Loren James Rittle
1999-09-30 18:02 ` Wes Morgan
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=200006111338.PAA26714@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=gcc@gcc.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.
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).