bzr log failure when filename specified and ghosts present.
Bug #209948 reported by
Xavier Maillard
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Critical
|
John A Meinel |
Bug Description
With recent bzr.dev, bzr log will throw an exception if --limit argument is too high.
bzr log --limit=30 --short bzrlib/
Changed in bzr: | |
importance: | Undecided → High |
milestone: | none → 1.4 |
status: | New → Confirmed |
Changed in bzr: | |
importance: | High → Critical |
Changed in bzr: | |
milestone: | 1.4 → 1.4rc2 |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I guess it is a regression since this works perfectly with bzr 1.3