monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Re: network costs of history copying (was Re: Monotone


From: Nathaniel Smith
Subject: [Monotone-devel] Re: network costs of history copying (was Re: Monotone server unreachable)
Date: Wed, 18 Jan 2006 10:11:06 -0800
User-agent: Mutt/1.5.9i

On Wed, Jan 18, 2006 at 12:39:12PM -0500, Frank Ch. Eigler wrote:
> 
> Nathaniel Smith <address@hidden> writes:
> 
> > [...]  It's also worth noting that you never need to pay this cost
> > again, whereas with a system like CVS every time you want another
> > working dir to work on a branch or the like, you have to do a new
> > checkout from scratch.  [...]
> 
> More sophisticated users of CVS may first duplicate an existing
> working tree to use as the basis of a large new branch checkout.  Then
> again, since cvs checkouts are so fast (relative to monotone, say),
> there is often little need for this.

Fair enough -- I probably should have mentioned something like that.
But as you say, most people don't do it in practice, so for purposes
of comparing bandwidth and seeing how plausible monotone's basic
design is, it is possibly fair.

I should also point out that making a second monotone checkout, the
case we're talking about here, is _much_ faster than cvs and does not
involve the network at all...

-- Nathaniel

-- 
"Of course, the entire effort is to put oneself
 Outside the ordinary range
 Of what are called statistics."
  -- Stephan Spender




reply via email to

[Prev in Thread] Current Thread [Next in Thread]