RFC: Transparent subrepository support by match module

[Mads Kiilerich]

  Martin Geisler wrote, On 08/18/2010 12:50 PM:
> Didly Bom<didlybom at gmail.com>  writes:
>> On Wed, Aug 18, 2010 at 9:59 AM, Martin Geisler<mg at lazybytes.net>  wrote:
>>> So perhaps one could extend the '**' and '*' glob operators by adding
>>> a lazy forms: '**?' and '*?' which then wont expand across
>>> subrepository boundaries. This is inspired by regexps where the '*?'
>>> is a non-greedy version of the '*' character.
>> I like this idea. It seems powerful yet easy to understand.
> I just had a better idea:
>
> - "*" matches all characters except "/"
> - "**" matches all characters including "/", but stops at subrepos
> - "***" matches everything

I agree that the matcher should recurse when for example commit recurse. 
I think there should be a general flag for enabling/disabling recursion 
everywhere, but why do we need other and special syntax for stopping 
recursion at subrepo borders? I think it adds unneeded complexity and we 
don't want it.

/Mads