Sub-repos marked dirty when they aren't. Sometimes leads to empty changeset

Issue #19 invalid
Former user created an issue

I am using mercurial 1.6.4 and TortoiseHG 1.1.4. When I do a commit on a master repo it sometimes shows some of the sub-repos as dirty, even though there are no changes in them.

In one case it just checked in an empty changeset in only one of the three sub-repos that it indicated were dirty and thus triggred a change to the .hgsubstate file in the master as well. The funny thing is that THG claimed "No changes" when we told it to comming, yet checking the repo history it is clear that an empty changeset was created.

Comments (2)

  1. Steve Borho

    THG gets the 'subrepo dirty' status directly from Mercurial, so there should be no difference between our behavior and command line behavior.

    It's possible the checked out revision of the subrepo had changed, and that's what made them dirty. The Qt version of the commit tool makes this more obvious.

    Lastly, this is the issue tracker for the Qt port. If you are using 1.1.4, the bug should be opened on the stable repository.

    My suggestion is to wait until you see the commit tool in this state, then try doing a commit on the command line and see if the results are the same.

  2. Log in to comment