[PATCH] subrepo: look for local pull source first

Mads Kiilerich mads at kiilerich.com
Mon Mar 28 10:47:50 CDT 2011


On 03/28/2011 04:08 PM, Martin Geisler wrote:
>>>> Why can't people just start using trivial paths?
>>> You cannot use trivial 'sub = sub' paths on a service like Bitbucket.
>>
>> I heard that kiln now supports nested subrepos. Congratulations! That
>> means that either bitbucket (and googlecode) or their users has to get
>> moving!
>>
>> It doesn't make sense that we add complexity to Mercurial 1.9 when the
>> real solution is that the hosting sites start supporting nested
>> subrepos. When they do it properly it will (in principle) work with
>> Mercurial since 1.3.
>
> Hmm, well... I don't really see it as that much complexity. The
> conceptual change I'm trying to make is to change the .hgsub file from
> being the only source of changeset and instead make it a fallback.

It puzzles me that the best solution to the problem gets so little 
attention. Repeat after me: ALWAYS! USE! TRIVIAL! SUBREPO! PATHS! ;-)

I will not support you in your quest for changing .hgsub to being a 
fallback, but I would perhaps be +0 for making it possible to explicitly 
in .hgsub specify a list of source paths that could be searched in 
order. That could perhaps have just as much (or little) relevance in all 
other places where paths are specified.

/Mads


More information about the Mercurial-devel mailing list