Any way to relate repos w/o cloning?

[Ted Pavlic]

> I don't think you want the 2 heads. If you remove your .hg, copy .hg from
> the other machine and do 'hg stat', then you'll see your modified files.
> Otherwise your repo will contain 2 useless copies of every file polluting
> the history and wasting space.

It's important to emphasize that these steps (manual copying) should 
only occur *once* just to make sure both developers are working from the 
same repo. That is, if the two developers can get each of their working 
directories into a matching state, then ONE of them can create an hg 
repo there ("hg init") and the other one can clone that repo. Then each 
can go about their own way, committing their own local changesets and 
pulling in remote changesets.

So copying (or whatever you prefer) should only be used to get the 
shared repo into a common state on which changesets can be added (which 
will create heads as necessary, but those heads can be brought back into 
the "trunk" with a merge).

--Ted


-- 
Ted Pavlic <ted at tedpavlic.com>