On Wednesday 11 April 2007 05:14:43 walt wrote:
Yes, I'm way off topic here, and I apologize -- but I've seen your
posts in the 'git' mail-list and you've experimented with Hg, so I
know you have your own opinions on version control systems.
Linus avoided rsync in favor of http in 'git'
walt wrote:
Linus avoided rsync in favor of http in 'git' because he thinks
rsync is inherently unreliable. I have *no* idea if he is right or
wrong in his opinions, but I figure you guys will favor me with your
own opinions on the subject.
Possibly for transferring the git objects. They
: Re: comparing cvsup vs. rsync
walt wrote:
Linus avoided rsync in favor of http in 'git' because he thinks
rsync is inherently unreliable. I have *no* idea if he is right or
wrong in his opinions, but I figure you guys will favor me with your
own opinions on the subject.
Possibly
Nigel Weeks wrote:
Just having an idea about this...are there any files in the source tree that
exceed 32kbytes?
What if a database solution were created to:
Contain every version of every file of every branch in a nicely indexed
database table
The md5/sha256 of each entry mentioned above
512
Since cvsup is somewhat of a hassle to build, discussion comes up from
time to time about switching to rsync. Rsync is generally accepted as
slower/more resource intensive, but how much hasn't been quantified. I
wanted to look into this in as un-bikesheddy a way as possible...
I timed repeated
:I timed repeated retrievals of src from theshell.com over the past few
:weeks, and here's the result.
:
:Retrieving all of src:
:cvsup averaged about 11.5 minutes
:rsync averaged about 19 minutes
:
:Retrieving only the last 24 hours of changes:
:cvsup averaged about 18 seconds
:
On 4/11/07, Matthew Dillon [EMAIL PROTECTED] wrote:
We could just distribute the CVS tree and write a front-end utility
in csh or sh that we distribute along with the rest of the system
to do the nitty gritty work of actually checking something out into
/usr/src. In fact, I
Matthew Dillon wrote:
My only worry is figuring out how to run the rsync daemon safely.
I'm a bit paranoid about running things on crater but I do agree
that we would have to run the master rsync daemon there.
You can run rsyncd from inetd or standalone. If you're really[tm]
Dmitri Nikulin wrote:
We could just distribute the CVS tree and write a front-end utility
in csh or sh that we distribute along with the rest of the system
to do the nitty gritty work of actually checking something out into
/usr/src. In fact, I think that would be preferable.
On 2007 Apr 10 (Tue) at 18:03:49 +0200 (+0200), Simon 'corecode' Schubert wrote:
:cvsync does cvs-only (so,
:like rsync), but it has a bug which breaks the RCS files in some cases.
:The author didn't want to fix it though :/
Can you describe the bug? I've been using cvsync for local copies of
On Tue, April 10, 2007 11:32 am, Matthew Dillon wrote:
We could just distribute the CVS tree and write a front-end utility
in csh or sh that we distribute along with the rest of the system
to do the nitty gritty work of actually checking something out into
/usr/src. In fact,
Peter Hessler wrote:
On 2007 Apr 10 (Tue) at 18:03:49 +0200 (+0200), Simon 'corecode' Schubert wrote:
:cvsync does cvs-only (so,
:like rsync), but it has a bug which breaks the RCS files in some cases.
:The author didn't want to fix it though :/
Can you describe the bug? I've been using
I am now running an rsync server on crater.dragonflybsd.org, serving
the cvs repository as 'dragonfly_cvs'.
rsync -a rsync://crater.dragonflybsd.org/dragonfly_cvs blahblah
--
Unfortunately I don't know how to get rsyncd to just log statistics
on completion, and it
Matthew Dillon wrote:
I am now running an rsync server on crater.dragonflybsd.org, serving
the cvs repository as 'dragonfly_cvs'.
rsync -a rsync://crater.dragonflybsd.org/dragonfly_cvs blahblah
very nice! will immediatelly switch to rsync operation. however, i'll have to
find
Matthew Dillon wrote:
I am now running an rsync server on crater.dragonflybsd.org, serving
the cvs repository as 'dragonfly_cvs'.
rsync -a rsync://crater.dragonflybsd.org/dragonfly_cvs blahblah
Matt,
something is weird with the permissions:
%rsync
Simon 'corecode' Schubert wrote:
I am now running an rsync server on crater.dragonflybsd.org, serving
the cvs repository as 'dragonfly_cvs'.
rsync -a rsync://crater.dragonflybsd.org/dragonfly_cvs blahblah
very nice! will immediatelly switch to rsync operation. however, i'll
:Matt,
:
:something is weird with the permissions:
:
:%rsync crater.dragonflybsd.org::dragonfly_cvs/src/crypto/heimdal/Attic/
:drwxrwxr-x1024 2005/03/28 05:35:43 .
:-r--rw-r-- 20313 2005/03/28 05:35:43 ChangeLog,v
:[..]
:-r-xrwxr-x3242 2005/03/28 05:35:43 compile,v
:
:why
17 matches
Mail list logo