subrepos: recursive status/diff with ui.commitsubrepos=True

[David.Sedlock at lantiq.com]

> -----Original Message-----
> From: Matt Mackall [mailto:mpm at selenic.com]
> Sent: Monday, December 05, 2011 9:06 PM
> To: Sedlock David (LQKG IT RDS)
> Cc: mg at aragost.com; mercurial-devel at selenic.com
> Subject: RE: subrepos: recursive status/diff with ui.commitsubrepos=True
> 


> But I've found another
> take on it that I think will work:
> 
> [experimental]
> subrepo = True
> 
> (read as "enable the under-development features of subrepos")
> 
> The plan here is that we'll stage a bunch of features to enable
> consistent recursive subrepos and once testers are fairly satisfied that
> the given batch is reasonable, we'll migrate it into the default
> behavior. Then we'll start adding new features under the same flag.

I'm not sure if this will help because I don't know what the meaning/effect of the option is supposed to be. We don't want to change the _default_ behavior from non-recursive to recursive. If experimental.subrepo has the same effect as adding --subrepos to commands, then this is fine, but I don't understand what is experimental about it. If the idea of calling it experimental is that it will go away one day because the default behavior will become recursive, then I don't agree at all, because I think the default behavior should remain recursive, even after all commands gracefully handle recursion. After years of using subrepos with non-recursion as the default it would be a big shock to suddenly find that the default is recursion, so I don't think you have this in mind.

Maybe you could just explain the exact meaning/effect of the option and state whether you intend the default behavior to remain non-recursive.

-David