From: Robert Lipe <robertl@dgii.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Jeffrey A Law <law@cygnus.com>, egcs@cygnus.com
Subject: Re: Direct CVS Access to egcs sources
Date: Sat, 17 Jan 1998 01:40:00 -0000 [thread overview]
Message-ID: <19980116095912.24987@dgii.com> (raw)
In-Reply-To: <199801142227.OAA03716@cygnus.com>
> could you setup a simple webpage which links in all the current ChangeLogs
> from the cvs tree? Something like:
>
> ChangeLog
> gcc/ChangeLog
> libio/ChangeLog
> etc.
Actually, if you have CVS access, that may be less interesting than
you think. (But potentially still useful.) Since the CVS logs from
those files essentially *are* those files, I've found that:
cvs log gcc/ChangeLog | paging filter of your choosing
is quite handy in telling me if I want to bother with an update/build/test
before I even start it.
For example:
(robertl) rjlhome:/play/egcs/gcc
$ cvs status ChangeLog
===================================================================
File: ChangeLog Status: Needs Patch
Working revision: 1.604
Repository revision: 1.609 /egcs/carton/cvsfiles/egcs/gcc/ChangeLog,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
This tells me the last time I refreshed, gcc's ChangeLog was at
version 1.604. The last checked in versino is 1.609. When I
do the 'cvs log', I can see the changes made since 1.604 and decide
if I want to refresh or not.
Now, with that said, if you want automated ChangeLog entries, there
is a decent tool to do it. Look at
http://eivind.imm.dtu.dk/cvs2html/
It's easy enough to invoke either via a cron job or via th ecvs loginfo
mechanisms.
next prev parent reply other threads:[~1998-01-17 1:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-13 4:52 Jeffrey A Law
1998-01-14 8:18 ` Oleg Krivosheev
1998-01-14 8:42 ` Jeffrey A Law
1998-01-15 16:06 ` Joe Buck
1998-01-15 16:30 ` Jeffrey A Law
1998-01-16 1:51 ` Joe Buck
1998-02-08 0:29 ` Jeffrey A Law
1998-02-08 7:13 ` Gerald Pfeifer
1998-02-08 8:57 ` Dave Love
1998-02-08 10:14 ` Jeffrey A Law
1998-02-08 13:23 ` H.J. Lu
1998-02-08 15:38 ` Bryan W. Headley
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 15:20 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 18:35 ` Todd Vierling
1998-01-17 22:30 ` Raja R Harinath
1998-01-15 16:30 ` Robert Lipe
1998-01-16 2:26 ` Jeffrey A Law
1998-01-15 16:30 ` Franz Sirl
1998-01-17 1:40 ` Robert Lipe [this message]
1998-01-17 22:30 ` Joseph H. Buehler
1998-01-19 2:25 ` Robert Lipe
1998-01-19 2:30 ` Jeffrey A Law
1998-01-19 2:30 ` Fred Fish
1998-01-20 4:00 Mike Stump
[not found] <199801142227.OAA03715@cygnus.com>
1998-01-23 0:20 ` Jeffrey A Law
1998-01-23 11:15 ` Franz Sirl
[not found] <199801231742.JAA01350@cygnus.com>
1998-01-23 9:47 ` Jeffrey A Law
[not found] <19980209020929.50632@cerebro.laendle>
1998-02-08 22:42 ` Jeffrey A Law
1998-02-09 19:49 ` Joern Rennecke
1998-02-09 21:34 ` Jeffrey A Law
1998-02-11 10:25 ` Marc Lehmann
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=19980116095912.24987@dgii.com \
--to=robertl@dgii.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=egcs@cygnus.com \
--cc=law@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).