Best way to cherrypick revisions?

[Alexander Belchenko]

Look at rebase plugin. You may find its `replay` command useful to 
manipulate with the history. Just be aware: rebased/replayed revisions 
will have all meta info as original revision except revision id. So both 
original and rebased copy will be different revisions for bzr, i.e. 
history will diverge, and you need to merge 2 branches later.

Also you may interesting in using Daggy Fixes workflow for further work.
http://www.monotone.ca/wiki/DaggyFixes/

Geoff Bache пишет:
> Hi all,
> 
> I find myself in the following situation. I have made a public release
> of my software (without branching) and since then done some
> development, and then fixed some bugs. I'd now like to make a branch
> containing just the bugfixes.
> 
> Essentially, if I have a branch with 3 revisions, I want to be able to
> create a Bazaar branch containing revisions 1 and 3 but not revision
> 2. And I'd like to keep the original checkin information if possible,
> authors, comments etc.
> 
> Is there any easy way to do this? I can get the files OK with bzr
> merge -c, but that seems to lose all the checkin information. I've
> tried using bzr send also, but Bazaar doesn't seem to accept merge
> directives with a "base revision" that isn't present in the target
> branch.
> 
> Regards,
> Geoff Bache
> 
>