Updating Mercurial: The Definitive Guide

Na'Tosha Bard natosha at unity3d.com
Wed Aug 24 05:00:34 CDT 2011


On Wed, Aug 24, 2011 at 4:26 AM, Matt Mackall <mpm at selenic.com> wrote:

>
> ..which will be just as true of a centralized system. The real issue is
> that these files break the central 'keeping a local copy of everything
> is fast/cheap' tradeoff.
>

This is certainly true.  But often is the case that the large binaries
aren't updated all that frequently and users find they can actually still
perform many (if not all) of the local operations that they normally would
when disconnected from the central server/share.

And the tradeoff is also one that teams may be willing to make, especially
when it comes with other benefits over a centralized system (e.g, sane
branching and merging, extensibility, the ability to share changes between
to local machines without revealing them to the central repository, etc).

Cheers,
Na'Tosha

-- 
*Na'Tosha Bard*
Build & Infrastructure Developer | Unity Technologies

*E-Mail:* natosha at unity3d.com
*Skype:* natosha.bard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20110824/a8befed3/attachment.html>


More information about the Mercurial-devel mailing list