Use of --follow breaks output on Mercurial >= 3.4.2

Andrew Hughes gnu.andrew at redhat.com
Thu Nov 19 01:45:38 UTC 2015


Hi,

I've just hit the same problem described in [0], which doesn't
seem to have been fixed.

For index.html, the script currently produces hg calls like:

hg log --follow  --rev 114 --rev 115 --rev 116 --rev 117 --rev 118 --rev 119 --rev 120 --rev 121 --rev 122 --rev 123 --template 'rev {rev} : {desc}' .hgtags

when doing a run to push a batch of committed changesets.

On both Mercurial 3.4.2 and 3.6.1, the --follow causes it to ignore the revisions
and just print the whole history of the file. Dropping it makes it work as it should and the
webrevs I just posted for 6 [0] look a lot better. It was previously used to
follow files across renames, and I even had it turned on by default for that
reason, but they changed the semantics in Mercurial.  I think I'd rather it
was right for most files and the odd history from a moved file was missing.
It seems unlikely someone would alter a file and then move it in the same
set of changesets anyway. Going by what the Mercurial developers say, the
fact it worked at all before was by chance, not design.

[0] http://mail.openjdk.java.net/pipermail/webrev-dev/2015-November/000134.html
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222

PGP Key: rsa4096/248BDC07 (hkp://keys.gnupg.net)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07



More information about the webrev-dev mailing list