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
# test that we don't interrupt the merge session if
# a file-level merge failed
hg init repo
cd repo
echo foo > foo
echo a > bar
hg ci -Am 'add foo'
hg mv foo baz
echo b >> bar
echo quux > quux1
hg ci -Am 'mv foo baz'
hg up -qC 0
echo >> foo
echo c >> bar
echo quux > quux2
hg ci -Am 'change foo'
# test with the rename on the remote side
HGMERGE=false hg merge
hg resolve -l
# test with the rename on the local side
hg up -C 1
HGMERGE=false hg merge
echo % show unresolved
hg resolve -l
echo % unmark baz
hg resolve -u baz
echo % show
hg resolve -l
hg st
echo % re-resolve baz
hg resolve baz
echo % after
hg resolve -l
echo % resolve all warning
hg resolve
echo % resolve all
hg resolve -a
echo % after
hg resolve -l
true