Re: decentralized version control with hg [was: N3 in JSON, euler.py ...]

On Mon, 2006-12-18 at 17:38 -0600, Dan Connolly wrote:
> On Sun, 2006-12-17 at 02:45 +0100, jos.deroo@agfa.com wrote:
> [...]
> > > For the moment I've put the new version at
> > 
> > http://eulersharp.cvs.sourceforge.net/*checkout*/eulersharp/2005/11swap/euler.py?revision=1.49
> > and the differences are
> > http://eulersharp.cvs.sourceforge.net/eulersharp/2005/11swap/euler.py?r1=1.46&r2=1.49
> > (and will try a hg push when http://homer.w3.org:8765/ runs)
> 
> OK, I started that hg serve process again.

I nuked that little history with just 2 versions and replaced
it by a full history of 2005/11swap, created using the attached
tailor config.

21:19:52 [I] Update completed, now at revision "2006-12-17 23:03:58 by
josd"

http://homer.w3.org:8765/?cs=44342a036620

I'm using the debian version of tailor:

Package: tailor
Version: 0.9.26-2
Depends: python (>= 2.4), python-support (>= 0.2)
Suggests: cvs, subversion, darcs, mercurial, monotone, codeville, bzr,
bazaar, cogito, tla
Description: migrate changesets between version control systems
  Homepage: http://www.darcs.net/DarcsWiki/Tailor


Some repository converstion tools rely on a local copy of
the CVS history. I learned sourceforge supports rsync
of the CVS history a la:

  rsync -av
rsync://eulersharp.cvs.sourceforge.net:/cvsroot/eulersharp/ .

I used that with cvs20hg to make a copy of the history
without the deployment/*.zip nor the jpywork stuff, but
I'm not sure how to keep in sync going forward without
the full history.


>  But don't try to push to it;
> you're not authorized.
> 
> Instead, just clone it:
> 
>   % hg clone http://homer.w3.org:8765/ euler-py-hg
> 
> and then make your changes and commit them. Then you can send
> them back to me in any number of ways:
> 
>  (1) hg export > patch
>   and mail me/us the patch
>  (2) hg bundle http://homer.w3.org:8765/ >bundle
>   and mail me/us the bundle, or stick it on a web site
>  (3) run an hg serve process of your own
>  (4) set up hg to run as a CGI script.
> 
> I see a new and particularly relevant topic in the mercurial wiki:
>   http://www.selenic.com/mercurial/wiki/index.cgi/UnderstandingMercurial
> 
> And for basic stuff, see...
>   http://www.selenic.com/mercurial/wiki/index.cgi/QuickStart
>   <- http://www.selenic.com/mercurial/
>     <- http://homer.w3.org:8765/
> 
-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E