<br><br><div><span class="gmail_quote">2008/3/7, Paul Franz <<a href="mailto:theandromedan@gmail.com">theandromedan@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> <br> Giorgos Keramidas wrote:<br> > On 2008-03-07 08:06, Peter Arrenbrecht <<a href="mailto:peter.arrenbrecht@gmail.com">peter.arrenbrecht@gmail.com</a>> wrote:<br> ><br> >> On Fri, Mar 7, 2008 at 5:28 AM, Paul Franz <<a href="mailto:theandromedan@gmail.com">theandromedan@gmail.com</a>> wrote:<br>
>><br> >>> I ask because I have a large<br> >>> ClearCase installation that I am looking to move to Mercurial. But I want to<br> >>> make sure of two things:<br> >>><br> >>> 1) It can clone the repository relatively quickly to our development team in<br>
>>> India (i.e. half a world away)<br> >>><br> >> If you have already created an hg version of your repo, I think using<br> >><br> >> hg init temp<br> >> hg -R temp in --bundle wiredata.bundle my-master-repo<br>
>><br> >> will create in wiredata.bundle the exact data stream that would go<br> >> over the wire for the actual repo data.<br> >><br> ><br> > Yes, indeed. But this will create a bundle with *all* the commits in a<br>
> tree, including ones which have possibly been pushed out already to the<br> > development team in India.<br> ><br> > In newer versions of Mercurial, you can also do this without the extra<br> > 'empty' workspace, by using the --all option of `hg bundle':<br>
><br> > % cd /ws/foo-project/releases/1.0-patches<br> > % hg bundle --all /var/tmp/wiredata.bundle<br> ><br> > The initial `hg clone' of a repository may take a while, depending on<br> > the link speed. Subsequent `pull' operations are blazingly fast though.<br>
> I am pulling changes from the OpenSolaris source tree every week or so.<br> > The current OpenSolaris source repository contains a little over 6,000<br> > changesets for more than 40,000 files. A `pull' completes on my home<br>
> DSL link in a few seconds (i.e. less than half a minute).<br> ><br> > Creating a *full* clone over SSH to <a href="http://hg.opensolaris.org">hg.opensolaris.org</a> may take a while<br> > though.<br> ><br>
> One of the easy ways to create *many* local clones in India is to create<br> > a hierarchy of `workspaces'. One can install a local `gate' in India,<br> > and use the gate only for pulling changes from the official tree. The<br>
> local India developers can clone the local gate instead of the remote<br> > `master' tree.<br> ><br> ><br> <br>So the local India developers would pull from the local gate repository<br> but push to the one in the US, correct?<br>
<br><br> Paul Franz<br> <br><br> _______________________________________________<br> Mercurial mailing list<br> <a href="mailto:Mercurial@selenic.com">Mercurial@selenic.com</a><br> <a href="http://selenic.com/mailman/listinfo/mercurial">http://selenic.com/mailman/listinfo/mercurial</a><br>
</blockquote></div><br>Or they push to the local gate and a "integrator" takes care to sync the local gate with the "master" in the US (on demand or on a regular schedule). That's what we do in my company with a team in Germany and one in Romania.<br>
<br>Peter<br><br>