Mercurial > hg
view templates/monoblue/index.tmpl @ 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 | 8b47efdf40ee |
children | 1de6e7e1bb9f |
line wrap: on
line source
{header} <title>{repo|escape}: Mercurial repositories index</title> </head> <body> <div id="container"> <div class="page-header"> <h1>Mercurial Repositories</h1> <ul class="page-nav"> </ul> </div> <table cellspacing="0"> <tr> <td><a href="?sort={sort_name}">Name</a></td> <td><a href="?sort={sort_description}">Description</a></td> <td><a href="?sort={sort_contact}">Contact</a></td> <td><a href="?sort={sort_lastchange}">Last change</a></td> <td> </td> <td> </td> </tr> {entries%indexentry} </table> <div class="page-footer"> {motd} </div> <div id="powered-by"> <p><a href="http://www.selenic.com/mercurial/" title="Mercurial"><img src="{staticurl}hglogo.png" width=75 height=90 border=0 alt="mercurial"></a></p> </div> <div id="corner-top-left"></div> <div id="corner-top-right"></div> <div id="corner-bottom-left"></div> <div id="corner-bottom-right"></div> </div> </body> </html>