lp:~jeff-licquia/bzr-bisect/yesno
- Get this branch:
- bzr branch lp:~jeff-licquia/bzr-bisect/yesno
Branch merges
- Bazaar Developers: Pending requested
-
Diff: 69 lines (+37/-2)2 files modifiedcmds.py (+5/-2)
tests.py (+32/-0)
Related bugs
Bug #1051395: meaning/usage of "yes" and "no" are unclear | Undecided | Confirmed |
Related blueprints
Branch information
Recent revisions
- 85. By Jeff Licquia
-
Don't hardcode the association between "yes" and "high revision".
Originally, the intent was for "yes" and "no" to mean whatever the user
wanted it to mean, and figure out at runtime whether that made "yes" or
"no" the high rev. This feature was lost at some point (if it ever
existed) and "yes" was assumed to mean "high rev". This was confusing,
because the docs implied you could make "yes" or "no" mean whatever you
wanted.Now, we figure out from the bisect log which identifier is high, and
stick with that moving forward. Also, there's now a test testing the
"no is high" case. - 78. By Jelmer Vernooij
-
Merge several improvements from Gustaf:
* Several testcases for running a test script.
* Fix up doc string format to be the same as other bzr plugins and core.
* Avoid deprecated bzrlib.trace.info.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:bzr-bisect