lp://staging/~amanica/bzr/320119-log_exclusive_lower_bound

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #320119: log uses inclusive revision ranges; inconsistent with other commands

Medium

Fix Released

Link a bug report

Related blueprints

4534. By Marius Kruger on 2009-08-03

start adding optional exclusive_start params to api's

4533. By Marius Kruger on 2009-08-01

merge with bzr.dev

4532. By Marius Kruger on 2009-08-01

maybe I should preserve the current show_log functionality so that I don't break everything

4531. By Marius Kruger on 2009-08-01

remove test that failes if we log from rev 0, which is now allowed

4530. By Marius Kruger on 2009-08-01

we now need to check if we are only logging the NULL_REVISION when determining the range

4529. By Marius Kruger on 2009-08-01

we cant determine if we only need to log a single revision so easily
* move exclude-with-merges to its own section, the inclusive one can probably be deprecated at some point?!
* we don't need to check if start_rev_id=end_rev_id in builtins.py

4528. By Marius Kruger on 2009-07-27

when revs are not None and equal, we have an empty set of revs

4527. By Marius Kruger on 2009-07-27

* allow revspec to return revno 0 for -4 when there are 3 revs, which is needed when using exclusive lower bounds.
* update more tests because of exclusive lower bounds.
* add failing test for log -r -1.. which should return nothing

4526. By Marius Kruger on 2009-07-27

fix some more tests because of exclusive lower bound

4525. By Marius Kruger on 2009-07-27

since the lower bound is now exclusive we can allow logging from the null revision