hg diff in the presence of subrepositories

Mads Kiilerich mads at kiilerich.com
Mon Jun 13 16:43:51 CDT 2011

paul_nathan at selinc.com wrote, On 06/10/2011 09:55 PM:
> The problem is:
> Notice that there is an inconsistency of operation here: hg diff is 
> not telling the user that there really is a difference in the world of 
> the top repository. Nor is hg status.
> Yet, the connotation and denotation of the words say that they tell 
> you the status and the difference. But they return that there is _no_ 
> difference.

Yes - see http://mercurial.selenic.com/wiki/Subrepository#Caveats . You 
might also be able to find this or something similar in the bug tracker.

> While this may make sense from an implementation standpoint(and it 
> does, if I think like an implementer),  I have received this question 
> from multiple people who are
> experienced, skilled and qualified software engineers who have used 
> other version control systems (ClearCase, SVN, git).
> From my perspective as a support person for hg in my company, this is 
> essentially a bug in the user experience and user interface.
> If there are subtle tricks I have not yet uncovered to make this plain 
> to the user I support,  I would like to hear them.

Subrepos might be a pain, but it is not an itch people like to scratch 
in their spare time. So I guess the trick is that the corporations that 
use them should sponsor the features they need. See 
http://mercurial.selenic.com/wiki/Support .

The challenge will not be to solve the problem in a way that works you, 
but it will be hard to solve it in a way that meets the quality 
requirements of the Mercurial project.


More information about the Mercurial mailing list