1. Summarise the issue (what were doing, what went wrong?)
For instance, in the darcs repo (with no changes)
ben@sarun: .../darcs/screened > time darcs whatsnew --look-for-moves
darcs whatsnew --look-for-moves 71,03s user 0,25s system 99% cpu
2. What behaviour were you expecting instead?
It should complete in a reasonable amount of time or at least tell me
that the operation might take a long time.
3. What darcs version are you using? (Try: darcs --exact-version)
The latest from screened.
The following patch sent by Guillaume Hoffmann <email@example.com> updated issue Issue2411 with
* resolve Issue2411: ignore swap moves with --look-for-moves
it was an extreme case anyway, and it made move detection
very slow in common cases