view tests/test-diff-hashes.out @ 8849:80cc4b1a62d0

compare grep result between target and its parent

I found that typical case is that grep target is added at (*) revision
in the tree shown below.

     +--- 1(*) --- 3
     0
     +--- 2 ------ 4

Now, I expect 'hg grep --all' to show only rev:1 which is first
appearance of target line.

But 'hg grep --all' will tell:

  target line dis-appeared at 3 => 4
  target line     appeared at 2 => 3
  target line dis-appeared at 1 => 2
  target line     appeared at 0 => 1

because current 'hg grep' implementation compares not between target
revision and its parent, but between neighbor revisions in walkthrough
order.

I checked performance of this patch by "hg grep --follow --all
walkchangerevs" on whole Mercurial repo, and patched version could
complete as fast as un-patched one.

found: No such file or directory
not: No such file or directory
quiet:
--- a/foo	Mon Jan 12 13:46:40 1970 +0000
+++ b/foo	Mon Jan 12 13:46:41 1970 +0000
@@ -1,1 +1,1 @@
-bar
+foobar

normal:
diff -r 74de3f1392e2 -r b8b5f023a6ad foo
--- a/foo	Mon Jan 12 13:46:40 1970 +0000
+++ b/foo	Mon Jan 12 13:46:41 1970 +0000
@@ -1,1 +1,1 @@
-bar
+foobar

verbose:
diff -r 74de3f1392e2 -r b8b5f023a6ad foo
--- a/foo	Mon Jan 12 13:46:40 1970 +0000
+++ b/foo	Mon Jan 12 13:46:41 1970 +0000
@@ -1,1 +1,1 @@
-bar
+foobar

debug:
diff -r 74de3f1392e2d67856fb155963441f2610494e1a -r b8b5f023a6ad77fc378bd95cf3fa00cd1414d107 foo
--- a/foo	Mon Jan 12 13:46:40 1970 +0000
+++ b/foo	Mon Jan 12 13:46:41 1970 +0000
@@ -1,1 +1,1 @@
-bar
+foobar