Issue 2392 trackdown --bisect could start at a given position

Title trackdown --bisect could start at a given position
Priority feature Status unknown
Milestone Resolved in
Superseder Nosy List imz, jaredj
Assigned To
Topics ProbablyEasy

Created on 2014-05-25.10:54:05 by imz, last changed 2014-05-25.10:54:05 by imz.

msg17480 (view) Author: imz Date: 2014-05-25.10:54:02
1. Summarise the issue (what were doing, what went wrong?)

As far as I understand from the manpage, "trackdown --bisect" would consider the whole set of patches in the repository. But if I know that at a certain point the test passed OK (e.g., in an older tagged release), I'd like to make it search only the limited set of patches (those which are not present in that set which is OK).

2. What behaviour were you expecting instead?

There is a way to specify the set of patched that are not interesting for the search (because they belonged to a release which was OK).

3. What darcs version are you using? (Try: darcs --exact-version)


4. What operating system are you running?

ALT Linux
Date User Action Args
2014-05-25 10:54:05imzcreate