tests/test-eol-hook
author Nicolas Dumazet <nicdumz.commits@gmail.com>
Sat, 03 Jul 2010 18:11:15 +0900
changeset 11608 183e63112698
parent 11249 0bb67503ad4b
permissions -rwxr-xr-x
log: remove increasing windows usage in fastpath The purpose of increasing windows is to allow backwards iteration on the filelog at a reasonable cost. But is it needed? - if follow is False, we have no reason to iterate backwards. We basically just want to walk the complete filelog and yield all revisions within the revision range. We can do this forward or backwards, as it only reads the index. - when follow is True, we need to examine the contents of the filelog, and to do this efficiently we need to read the filelog forward. And on the other hand, to track ancestors and copies, we need to process revisions backwards. But is it necessary to use increasing windows for this? We can iterate over the complete filelog forward, stack the revisions, and read the reversed(pile), it does the same thing with a more readable code.

#!/bin/sh

cat > $HGRCPATH <<EOF
[diff]
git = True
EOF

hg init main
cat > main/.hg/hgrc <<EOF
[extensions]
eol =

[hooks]
pretxnchangegroup = python:hgext.eol.hook
EOF

hg clone main fork

cd fork
cat > .hgeol <<EOF
[patterns]
mixed.txt = BIN
**.txt = native
EOF

hg add .hgeol
hg commit -m 'Commit .hgeol'

printf "first\nsecond\nthird\n" > a.txt
hg add a.txt
echo "% hg commit (LF a.txt)"
hg commit -m 'LF a.txt'
echo "% hg push"
hg push ../main

printf "first\r\nsecond\r\nthird\n" > a.txt
echo "% hg commit (CRLF a.txt)"
hg commit -m 'CRLF a.txt'
echo "% hg push"
hg push ../main


echo "% hg commit (LF a.txt)"
printf "first\nsecond\nthird\n" > a.txt
hg commit -m 'LF a.txt (fixed)'
echo "% hg push"
hg push ../main