Patchwork [04,of,10,V2] status: handle more node indicators in buildstatus

mail settings
Submitter Durham Goode
Date March 8, 2017, 3:22 a.m.
Message ID <>
Download mbox | patch
Permalink /patch/18979/
State Accepted
Delegated to: Martin von Zweigbergk
Headers show


Durham Goode - March 8, 2017, 3:22 a.m.
# HG changeset patch
# User Durham Goode <>
# Date 1488909371 28800
#      Tue Mar 07 09:56:11 2017 -0800
# Node ID 68644896cbdcfc956079662668e010038bfe8048
# Parent  ccec5eeceb85929c5df041b768d01694176b3a9d
status: handle more node indicators in buildstatus

There are several different node markers that indicate different working copy
states. The context._buildstatus function was only handling one of them, and
this patch makes it handle all of them (falling back to file content comparisons
when in one of these states).

This affects a future patch where we get rid of context._manifestmatches as part
of getting rid of manifest.matches(). context._manifestmatches is currently
hacky in that it uses the newnodeid for all added and modified files, which is
why the current newnodeid check is sufficient. When we get rid of this function
and use the normal manifest.diff function, we start to see the other indicators
in the nodes, so they need to be handled or else the tests fail.


diff --git a/mercurial/ b/mercurial/
--- a/mercurial/
+++ b/mercurial/
@@ -23,6 +23,7 @@  from .node import (
+    wdirnodes,
 from . import (
@@ -140,7 +141,7 @@  class basectx(object):
             elif flag1 != flag2:
-            elif node2 != newnodeid:
+            elif node2 not in wdirnodes:
                 # When comparing files between two commits, we save time by
                 # not comparing the file contents when the nodeids differ.
                 # Note that this means we incorrectly report a reverted change