[RFC] uncommit creates bundles

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bentley wrote:
> Hi all,
> 
> I just had a thought.  What if uncommit created bundles?
> 
> e.g.
> $ bzr uncommit
> 1 revision uncommitted:
>  1776 Aaron Bentley     2007-03-13
>       Introduce branch6
> The revisions have been backed up as uncommit-1.patch.  To restore them,
> do "bzr pull uncommit-1.patch".
> $
> 
> Uncommit wouldn't need to be interactive, because you could recover from
> mistakes easily.  It would mean that if you discovered a mistake later,
> you could still correct it.  And it would mean you could use "uncommit"
> more like "shelve"-- to temporarily remove revisions.
> 
> Aaron

Well, at this point, all we really need is for 'uncommit' to spit out
the revision id. So that you can do 'bzr pull -r revid:foo'.

Since uncommit doesn't remove anything from the repository.

Also, because we leave the working tree alone, the bundle wouldn't
actually directly apply to the working tree. (I guess it could, as long
as merge3 ignores exact change conflicts).

I kind of like that 'bzr uncommit' is *really* fast. Whereas if it had
to create a bundle it would actually be quite slow. (At least with our
current bundles.)

Just some thoughts on it. I certainly wouldn't block anything that
wanted to generate a bundle during uncommit.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF9rslJdeBCYSNAAMRAg/BAKCXuj5APiBUYtvRIFH7ZVX+0S5SSwCfT7LZ
rlzKqs0NBPwMw4PGuYixOtM=
=5irh
-----END PGP SIGNATURE-----