When using shelve with bzr-colo, it would be nice if a shelf could be placed on the branch instead of the checkout. This would allow scoping a shelf to a branch, rather than be universal to all the branches.
I doubt this ability would make sense for non-colocated branches though.
From an e-mail to <email address hidden> (Message-Id: <email address hidden>)
> I've just tried using bzr-colo to track changes to a CVS-based
> project. I've committed all the files in a bzr branch except the
> CVS detritus. The colo support is nice since some other tools I'm
> using for that project use the CVS detritus.
>
> I found that I had some testing code that I wanted to keep around
> but not actually commit to the branch. 'bzr shelve' came in handy
> for stashing that away. But I think it would work even better if
> the shelf could be associated with the colo branch rather than the
> checkout. I'm instead embedding the colo branch name in the shelf
> message.
Actually, it might also make sense when using switch with lightweight checkouts.
(I meant for this to be a wishlist, but I don't seem to have the ability to set that.)