Fwd: nuclear lauchcodes and nuclear waste

[Aaron Bentley]

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

John Arbash Meinel wrote:
> I'm not sure exactly what bzr is going to have (forcing a revision to
> become a ghost is a little bit tricky.)
> 
> But I just posted a [PLUGIN] to the list (which didn't get any hits),
> where I specifically implemented the ability to remove unused revisions
> from the store.

I think that in addition to this functionality, we may well want the
ability to re-do a particular revision, but leave the changes introduce
by later revision.  This operation would, naturally, produce new
revision-ids.

e.g.

$ bzr status
$ bzr do-over -r 100
Copying revision-history to old-revision-history
Uncommitting to revision 49
Reverting to revision 50
Ready to redo revision 50
$ bzr status
added files:
  nuclear-launch-codes
modified files:
  harmless-code
$ bzr revert nuclear-launch-codes
$ bzr status
modified files:
  harmless-code
$ bzr do-over --continue
Committing revision 100
Applying old 100-101
Committing revision 101
Applying old 101-102
Committing revision 102

etc.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDwttH0F+nu1YWqI0RAkycAKCBv9mIuhixv5YdaUt92vhg9XGonACfa0y/
LfxvhdBxYAVW5JgcKrkqRJw=
=7bE6
-----END PGP SIGNATURE-----