annotate tests/test-hgweb-no-request-uri.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.

changeset:   0:4cbec7e6f8c4
tag:         tip
user:        Testing
date:        Thu Jan 01 00:00:00 1970 +0000
summary:     test

---- HEADERS
200 Script output follows
---- DATA
[('Content-Type', 'application/atom+xml; charset=ascii')]
<?xml version="1.0" encoding="ascii"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 <!-- Changelog -->
 <id>http://127.0.0.1/</id>
 <link rel="self" href="http://127.0.0.1/atom-log"/>
 <link rel="alternate" href="http://127.0.0.1/"/>
 <title>repo Changelog</title>
 <updated>1970-01-01T00:00:00+00:00</updated>

 <entry>
  <title>test</title>
  <id>http://127.0.0.1/#changeset-4cbec7e6f8c42eb52b6b52670e1f7560ae9a101e</id>
  <link href="http://127.0.0.1/rev/4cbec7e6f8c42eb52b6b52670e1f7560ae9a101e"/>
  <author>
   <name>Testing</name>
   <email>&#84;&#101;&#115;&#116;&#105;&#110;&#103;</email>
  </author>
  <updated>1970-01-01T00:00:00+00:00</updated>
  <published>1970-01-01T00:00:00+00:00</published>
  <content type="xhtml">
   <div xmlns="http://www.w3.org/1999/xhtml">
    <pre xml:space="preserve">test</pre>
   </div>
  </content>
 </entry>

</feed>
---- ERRORS

---- HEADERS
200 Script output follows
---- DATA
[('Content-Type', 'text/plain; charset=ascii')]

-rw-r--r-- 4 bar


---- ERRORS

---- HEADERS
200 Script output follows
---- DATA
[('Content-Type', 'text/plain; charset=ascii')]

/repo/

---- ERRORS

---- HEADERS
200 Script output follows
---- DATA
[('Content-Type', 'text/plain; charset=ascii')]

-rw-r--r-- 4 bar


---- ERRORS