[PATCH] subrepo: look for local pull source first
mg at lazybytes.net
Wed Mar 30 12:39:57 CDT 2011
Matt Mackall <mpm at selenic.com> writes:
> On Wed, 2011-03-30 at 11:50 -0500, Kevin Bullock wrote:
>> > 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
> And it can also be done with hgweb mappings.
Oh... right, that is a new idea that I hadn't thought about -- thanks!
I think they will like this idea since it means that there is really
just a single repository on the server. I'll pass it along...
Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the Mercurial-devel