Direct CVS Access to egcs sources

[Robert Lipe]

> 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.