[Bug 5712] New: hg status --rev shows modified file when it's been reverted to a previous version and committed

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=5712

            Bug ID: 5712
           Summary: hg status --rev shows modified file when it's been
                    reverted to a previous version and committed
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: hg at pewpew.net
                CC: mercurial-devel at mercurial-scm.org

Created attachment 1980
  --> https://bz.mercurial-scm.org/attachment.cgi?id=1980&action=edit
modified test-status-rev.t showing the problem

This is somewhat similar to 522, I think, but not the same.

Explanation: committing a file, modifying it and committing the modification,
then reverting back to the original version seems to work just fine, until we
commit the "revert back to the original version", at which point `hg status
--rev <original_rev>` starts claiming that we've modified the file.

Since code is easier to understand than english, I've attached a modification
to test-status-rev.t that shows the problem. That version of the test currently
fails with this diff:

@@ -185,3 +185,4 @@

 BROKEN: Should be empty, is showing stuff.
   $ hg st --rev 0
+  M somefile
ERROR: test-status-rev.t output changed
!
Failed test-status-rev.t: output changed
# Ran 1 tests, 0 skipped, 1 failed.
python hash seed: 3135105629



hg version:
Mercurial Distributed SCM (version 4.3.2+596-b90bd9a98c8b)
(see https://mercurial-scm.org for more information)

Tests were written/run at: c212947273a7

-- 
You are receiving this mail because:
You are on the CC list for the bug.