[darcs-devel] [issue2541] whatsnew -l much slower in darcs 2.12.5

[Ben Franksen]

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

One obvious idea how to implement this is to extend the patch-index so
that it covers information about conflicts, too. However, I am uncertain
if this is possible: whether a patch touches a certain file is a
property of the patch itself; OTOH, wether it conflicts with another
patch (and which files exactly are conflicting) depends on the context,
too. Commuting a patch A past one with a conflict B might transfer the
conflict from B to A. It would be necessary to update the index in that
case, whereas with what the index currently tracks this would not be
necessary, right?

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