[RFC] Moving uncommited changes from a tree to another.

[John Arbash Meinel]

Aaron Bentley wrote:

...

> Aw shucks.  Of course, the problem is trying to maximize the
> functionality while minimizing the number of commands to learn.  Shove
> is a very single-purpose tool.  But if other folks feel 'shove' should
> go in core, I can prepare that.
> 
> Aaron

I'm +0 on it. It seems useful, though I just do:

cd new-tree
bzr diff ../other-tree | patch -p0
bzr revert ../other-tree

The way I would really use it, is more like 'bzr switch'. Where I want
to create a new branch, with this change pending, and leave the old
branch alone.
And really, it only needs to be done because of 'branch.nick'. (and
keeping the parent straight, I guess).


I don't know if 'revert' should use bundles. It might be a better way to
leave the working tree clean, though.

I just know all the problems Arch got into with 'undo', since it could
have invalid trees. And I wouldn't want to see revert get into that
trouble. (I realize it isn't really possible under bzr to have an
invalid tree, so we may be just fine)

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060809/720fe5c2/attachment.pgp