You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 1997/06/17 16:49:48 UTC

cvsup vs cvs

What exactly is the rationale for migrating to cvsup? Will the current
cvs setup be dismantled?

Building cvsup on other OSs ain't easy at all; Nope, not at all :-(
-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"

Re: cvsup vs cvs

Posted by Rob Hartill <ro...@imdb.com>.
On Tue, 17 Jun 1997, Marc Slemko wrote:

> No, cvsup goes on _top_ of CVS to allow easier access to the repository. 
> 
> The main use isn't for people who already have commit access, but it is
> intented to allow people who don't easier read-only access to the CVS
> tree.  Right now the only way is downloading the complete repository.
> That is bad, especially now that more people are joining the mailing list
> (with the combination of NT and the fact that it is now documented) and
> want to put their useful testing skills to work...

After a little help from Marc, I got cvsupd working for my own cvs
repositories (not apache stuff).

I've got a main repository at the end of a 28.8 modem and it was taking
me a good 2+ hours to do a "cvs -z update -Pd" on ~1.2mb of html in ~17,000
files.  With cvsupd it looks (from initial tests) like this will be reduced
to 5-10 minutes. woo hoo!.

cvsup saves bandwidth big time.



Re: cvsup vs cvs

Posted by Marc Slemko <ma...@worldgate.com>.
No, cvsup goes on _top_ of CVS to allow easier access to the repository. 

The main use isn't for people who already have commit access, but it is
intented to allow people who don't easier read-only access to the CVS
tree.  Right now the only way is downloading the complete repository.
That is bad, especially now that more people are joining the mailing list
(with the combination of NT and the fact that it is now documented) and
want to put their useful testing skills to work...

On Tue, 17 Jun 1997, Jim Jagielski wrote:

> What exactly is the rationale for migrating to cvsup? Will the current
> cvs setup be dismantled?
> 
> Building cvsup on other OSs ain't easy at all; Nope, not at all :-(
> -- 
> ====================================================================
>       Jim Jagielski            |       jaguNET Access Services
>      jim@jaguNET.com           |       http://www.jaguNET.com/
>             "Look at me! I'm wearing a cardboard belt!"
>