Conceptual Question about Repos and structuring development workspaces...

[Stuart W. Marks]

Sean wrote:
> Just to clarrify, if I make a repo at this level:
> 
> customer/abc/123/
> 
> Can I later decide that it really should have been made at this level
> 
> customer/abc/
> 
> and somehow move it ?

You can probably move it later, but it might be somewhat tedious. If you've 
create the repo at the "123" level, the contents of "123" will appear at the 
top level of the repo. You'd have to create a "123" subdirectory, move the top 
level contents there, and then add the remaining contents of the abc directory.

I'd suggest that you develop some automation (scripts, etc.) to convert your 
existing stuff to hg in a non-destructive way. That way you can tinker with the
setup, try out some operations, and if you don't like how it's working (or if 
you screw up) you can throw it away and start over.

> Does mercurial play nice with unison ?
> 
> I sync my entire customer tree to an external usb and carry it around 
> with me.

By unison, do you mean this one?

http://www.cis.upenn.edu/~bcpierce/unison/index.html

I think unison is a pretty good file synchronizer (I use it myself) but if you 
have your stuff in hg you don't need unison anymore. Once you have everything 
in hg, you can put repos on the USB drive and on your desktop (or whever) use 
hg operations to propagate changes back and forth. This is probably better than 
unison, since hg will merge non-conflicting changes and keep track of the 
history of all changes made.

s'marks