[RFC] Moving uncommited changes from a tree to another.
Kevin Smith
yarcs at qualitycode.com
Wed Aug 9 04:29:53 BST 2006
On Sun, 2006-08-06 at 16:25 +0200, Matthieu Moy wrote:
> I believe the best way to handle this would be:
>
> 1) allow revision bundles to refer to uncommited changes. I believe
> Robert's proposal to consider the working tree as a kind of
> particular revision goes in this direction too.
>
> 2) Have "bzr revert" leave a bundle of the state of the tree before
> revert somewhere.
>
> 3) Have a way to apply this bundle without creating a new revision. I
> mean, the changes should appear in the working tree as they used to
> be.
I'm not sure about the technical aspects, but 1+2 seem like an awkward
kludge from a user perspective.
Would it be possible to just have a command that converts the current
uncommitted changes to a bundle, and another that applies a bundle to
the working tree without committing?
Kevin
More information about the bazaar
mailing list