"bzr send" does not work with revision ranges

Bug #544126 reported by Ansgar Burchardt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

Summary:
It is currently not possible to specify revision ranges via "bzr send -r A..B" to forward only specific changes upstream.
I encountered this problem when commiting several (unrelated) changes locally that I wanted to forward to different bug reports.

How to reproduce:
1. Clone a repository.
2. Change and commit two files.
3. Execute "svn send -r last:2..last:1 -o test".
Note that test includes the changes from both commits.

Expected result:
The bundle should only contain the changes introduced in the last commit (cf. "bzr diff -r last:2..last:1"). Compare also with "git format-patch -1 <rev>".
At least "bzr send" should abort with an error instead of including more commits in the bundle.

Workaround:
Use branches (takes more of my time though) or use "bzr diff" and send only the patch upstream (and add commit message by hand).

Martin Pool (mbp)
tags: added: bundle
Changed in bzr:
status: New → Confirmed
importance: Undecided → Medium
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.