Issue 2426: with rebase in progress, --last is off by one - Darcs bug tracker

Title	with rebase in progress, --last is off by one
Priority		Status	duplicate
Milestone	2.10.0	Resolved in
Superseder	darcs changes --last n doesn't take account of rebase patch View: 2260	Nosy List	bfrk
Assigned To		Topics

Created on 2015-01-16.23:30:45 by bfrk, last changed 2015-02-18.01:52:54 by gh.

Messages
msg17939 (view)	Author: bfrk	Date: 2015-01-16.23:30:43
1. Summarise the issue (what were doing, what went wrong?) With a rebase in progress, e.g. darcs changes --last=n displays only n-1 patches. Same with diff and possibly other commands that support --last. 2. What behaviour were you expecting instead? That --last behaves as usual, e.g. list the last n changes. 3. What darcs version are you using? (Try: darcs --exact-version) 2.9.9 (+ 216 patches)
msg18147 (view)	Author: gh	Date: 2015-02-18.01:52:53
This seems to be the same as http://bugs.darcs.net/issue2260 .

History
Date	User	Action	Args
2015-01-16 23:30:45	bfrk	create
2015-01-26 20:32:31	gh	set	milestone: 2.10.0
2015-02-18 01:52:54	gh	set	status: unknown -> duplicate messages: + msg18147 superseder: + darcs changes --last n doesn't take account of rebase patch