[PATCH 1 of 1] Enable commit to disallow recursive submodule commits

Matt Mackall mpm at selenic.com
Tue Apr 27 14:07:37 CDT 2010


On Fri, 2010-04-23 at 19:10 -0500, Michael Ekstrand wrote:
> On 04/23/2010 12:53 PM, Matt Mackall wrote:
> > Let's focus on that instead. For starters, we need hg summary to tell us
> > about dirty subrepos (easy). And for commit to warn us about subrepos
> > it's committing (also easy). Then we need to figure out how to report
> > subrepos in status in a way that doesn't confuse all the GUI tools that
> > use it. That's a bit harder.
> 
> Currently, the code for subrepos has a single concept of "dirty", where
> the subrepo's state differs from its parent's notion, regardless of
> whether the working copy is dirty or not.  Would it be reasonable to
> suggest that the summary and status output and commit warnings make a
> distinction?  If the working copy has no uncommitted changes but has
> changed, then "committing" it (updating .hgsubstate) is exactly what I
> want to do.

I'm open to suggestions.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial-devel mailing list