subrepo grand plan
dirkjan at ochtman.nl
Thu Oct 20 13:37:38 CDT 2011
On Thu, Oct 20, 2011 at 19:24, Matt Mackall <mpm at selenic.com> wrote:
>> On Thu, Oct 20, 2011 at 17:32, Matt Mackall <mpm at selenic.com> wrote:
>> > We'd need to add a -S switch to get the old behavior and a hint.
>> > I'm a little concerned that this will bring development on subrepo
>> > integration to a stand-still.
>> Not sure what you mean? An -S switch for commit?
> $ hg commit
> abort: uncommitted subrepos
> (use commit --subrepo to get the behavior we took away)
>> Why would this bring
>> development to a stand-still? What kind of "integration"?
> If we do (b) now, the pressing need for (a) will vanish.
Right, so they will get added as people need them, which seems just
about right to me. The easy workaround is always cd subrepo; do your
thing there, which at least is trivial to learn (not as much so the
other way around).
It's your call, of course, but it seems to me making the hard choice
now will prevent a lot of agony (i.e. significant astonishment) later.
More information about the Mercurial-devel