[PATCH] subrepo: look for local pull source first
Kevin Bullock
kbullock+mercurial at ringworld.org
Wed Mar 30 11:50:18 CDT 2011
On Mar 30, 2011, at 3:01 AM, Martin Geisler wrote:
> Hi again,
>
> I asked my client to explain again why they want full paths in the
> .hgsub file. This is what they wrote (with my reply interleaved):
Thanks for writing this up. I have a feeling it will become a useful reference. Just one thing I'll note:
> [...]
> You can solve this with the standard share extension on the server. What
> it does is simple: it behaves as if the .hg folders were symlinked. We
> symlink the two clones of Component-X back to the top-level Component-X
> repository. So when Alice does
>
> $ cd Project-A/lib/X
> $ hg push http://server/Component-X
>
> then the changesets show up instantaniously in all three Component-X
> clones on the server. In particular, when Bob does
>
> $ cd Project-B/lib/X
> $ hg pull # no special path
>
> then he gets the changesets Alice just pushed.
It can also be done using *actual* symlinks on the server, linking the shared component repos into their appropriate relative locations in the project repos. This is how I have my 'canonical' repositories set up.
pacem in terris / mir / shanti / salaam / heiwa
Kevin R. Bullock
More information about the Mercurial-devel
mailing list