[Bug 3570] New: Incorrect hg log output

bugzilla-daemon at bz.selenic.com bugzilla-daemon at bz.selenic.com
Thu Aug 2 02:07:20 CDT 2012


          Priority: normal
            Bug ID: 3570
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Incorrect hg log output
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: al.drozdov at gmail.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

rev.e410be860393 introduced a bug in revision lookup if revision is specified
by full 40-digit hex hash.

changeset:   16745:e410be860393
user:        Bryan O'Sullivan <bryano at fb.com>
date:        Sat May 12 10:55:08 2012 +0200
files:       mercurial/parsers.c mercurial/revlog.py
revlog: speed up prefix matching against nodes

1. Create mercurial repository with commands:
hg init
touch a && hg add a && hg commit -m 'a'
touch b && hg add b && hg commit -m 'b'
touch c && hg add c && hg commit -m 'c'
touch d && hg add d && hg commit -m 'd'
hg up 1
touch e && hg add e && hg commit -m 'e'
touch f && hg add f && hg commit -m 'f'

2. Update to the latest revision:
hg up 5

3. Get revision 2 full hash:
export FULLREV=`hg log --template "{node}\n" -r 3`

4. Now test these two commands output. Results should be the same
   (empty set) but the second command returns revision 3:
hg log -q -r "3 and ancestor(3,.)"
hg log -q -r "$FULLREV and ancestor($FULLREV,.)"

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Mercurial-devel mailing list