On 17 Apr 2000, at 15:56, Larry Jones wrote:
>Sean Cavanaugh writes:
>>
>> I've decided its past time to setup an active CVS repository for CVS, so
>> I've created my own on sourceforge called 'Renegade CVS', the project name
>> is rcvs.
>
>If people want to fork CVS that's OK with me, but I hasten to point out
>that there *is* an active CVS repository (at cvs.cyclic.com), a group of
>developers, and ongoing maintenance.
>
One would be hard pressed to believe it!
I see postings to this mailing list and bugs-cvs indicating you and others have
applied bug fixes
and so on. But how is it possible to find out which bug fixes have been applied?
Yes, I know I can use cvs to get all the source. But I'm behind a firewall at work,
where I really
want it. and if I was to get the source from home (I have done it before), I've still
got to get it
work (it's too big to fit on a floppy). Plus it takes a not insubstantial time to
download and I
have to pay for every second of my online time.
Can we have daily snapshots, tar-ed and gzip-ed, of the source tree?
I'm sure a cron job could be used to do this?
In fact didn't you say that the source tree is built daily on all the supported
platforms?
Surely it's not too difficult to package those binaries for each platform into a
tarball and put
that into the ftp directory (over-writing yesterdays snapshot would be fine).
Ditto for the source tree.
Plus an online link to the changelog would be good.
And some idea of current and future plans would be good.
Mike,
--
Share what you know. Learn what you don't.
Mike Little <[EMAIL PROTECTED]>
work: <[EMAIL PROTECTED]>
Web: http://www.ampersoft.co.uk
PGP public key at http://www.ampersoft.co.uk/mike/mike.html
