view tests/test-rebase-conflicts.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.

1 files updated, 0 files merged, 0 files removed, 0 files unresolved
created new head
@  5: L3
|
o  4: L2
|
o  3: L1
|
| o  2: C3
|/
o  1: C2
|
o  0: C1


% Try to call --continue
abort: no rebase in progress

% Conflicting rebase
merging common
warning: conflicts during merge.
merging common failed!
abort: fix unresolved conflicts with hg resolve then run hg rebase --continue

% Try to continue without solving the conflict
abort: unresolved merge conflicts (see hg resolve)

% Conclude rebase
saving bundle to 
adding branch
adding changesets
adding manifests
adding file changes
added 3 changesets with 3 changes to 3 files
rebase completed
@  5: L3
|
o  4: L2
|
o  3: L1
|
o  2: C3
|
o  1: C2
|
o  0: C1


% Check correctness
  - Rev. 0
c1
  - Rev. 1
c1
c2
  - Rev. 2
c1
c2
c3
  - Rev. 3
c1
c2
c3
  - Rev. 4
resolved merge
  - Rev. 5
resolved merge