On Fri, Sep 05, 2003 at 01:09:00PM +0200, Felix K?hling wrote: > On Fri, 05 Sep 2003 11:57:57 +0100 > Keith Whitwell <[EMAIL PROTECTED]> wrote: > > > Felix Kühling wrote: > > > > > > > > > > I think the idea is that you mirror the entire CVS repository with > > > cvsup. Then you can do any read-only cvs operations on the local copy of > > > the repository. That includes merging branches in a working copy. For > > > commiting you still have to use the remote repository, though. > > > > So that's effectively the same as using rsync to mirror the repository, right? > > Right, but it's especially optimized RCS files. I found a detailed > explanation at www.cvsup.org. The most important points quoted: > > "CVSup is a software package for distributing and updating collections of > files across a network. ..." > > "... most likely the fastest mirroring tool in existence today." > > "CVSup parses and understands the RCS files making up a CVS repository. > When updates occur, CVSup extracts new deltas directly from the RCS > files on the server and edits them into the client's RCS files. ..." > > "To update non-RCS files, CVSup uses the highly efficient rsync > algorithm, developed by Andrew Tridgell and Paul Mackerras."
I have no problem in hosting a cvsup server as an option to the rsync mirror. But AFAICS its RCS features are useless here since there is no direct access to the SF CVS repository (the closest thing are the backup tarballs, but they're even more outdated than the anon cvs...). José Fonseca ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
