Mercurial > hg
comparison tests/test-grep.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.
author | FUJIWARA Katsunori <foozy@lares.dti.ne.jp> |
---|---|
date | Tue, 19 May 2009 16:49:54 +0900 |
parents | dac14cc9711e |
children | 717c35d55fb3 |
comparison
equal
deleted
inserted
replaced
8848:89b71acdac9a | 8849:80cc4b1a62d0 |
---|---|
36 adding noeol | 36 adding noeol |
37 % last character omitted in output to avoid infinite loop | 37 % last character omitted in output to avoid infinite loop |
38 noeol:4:no infinite loo | 38 noeol:4:no infinite loo |
39 % issue 685 | 39 % issue 685 |
40 adding color | 40 adding color |
41 colour:1:octarine | |
41 color:0:octarine | 42 color:0:octarine |
42 colour:1:octarine | 43 colour:1:octarine |
43 colour:1:octarine | 44 % issue 337 |
45 adding color | |
46 1 files updated, 0 files merged, 0 files removed, 0 files unresolved | |
47 created new head | |
48 1 files updated, 0 files merged, 0 files removed, 0 files unresolved | |
49 color:3:-:red | |
50 color:1:+:red |