[darcs-devel] [issue2574] unrecord -a --last=1 can be extremely inefficient

[Ben Franksen]

Ben Franksen <ben.franksen at online.de> added the comment:

Correction: it does not start behind the last tag. The first patch
mentioned (after the last one that is to be unrecorded) is

zcat
_darcs/patches/0000002054-b5af519485c5541ea7bb13a8811b79adc31132ccbda59e42c3d8ab6d2f4ae3e7
| head -3
[resolve issue2410: detect replaces even with tokens of different lengths
Guillaume Hoffmann <guillaumh at gmail.com>**20150217223248
 Ignore-this: 21859ec1e6a7652a68b4409c71dd08cd

I did a 'darcs log' and searched for the title of this patch and found
that tag '2.10.0' depends on it. So I made an experiment. I cloned the
repo up to the tag 2.10.0, then pulled the next tag which is 2.12.0,
then the rest. Then I did the same unrecord -a --last=1 again and this
time it terminated reasonably fast (considering that there are 500
patches since the last, now clean, tag and the inventory gets re-written
completely). When I use the --debug and the copyFileXxx filter it still
shows me 150 patches being copied.

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue2574>
__________________________________