bzr heads: how to kill uncommited revisions?

[Aaron Bentley]

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

Martin Pool wrote:
> On  2 Aug 2006, Michael Ellerman <michael at ellerman.id.au> wrote:
> 
>> I think in the medium term there must be a way to clean out unused
>> (unreferenced?) revisions in a shared repo. Simply in terms of space
>> you need to be able to do it, otherwise over time your repo will fill
>> up with lots of junk. And there might be people who have a legal
>> requirement that all code from branch x is physically removed.
> 
> I agree, and I filed https://launchpad.net/products/bzr/+bug/54870

Cool.  This one's never been a question of "whether", just a question of
"when".  Though personally, I'm not too worried about the space-wastage.
 Remember when our repositories were full-file copies of each version?

The problem of nuclear launch codes is the issue.  And btw, it's the
reason why branches must be inside the repository-- so we can determine
definitively which revisions are unused.

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

iD8DBQFE0BLa0F+nu1YWqI0RAgwrAJwJh0EUOwS9RMiv4rmwjZ6BTkWRiQCfdKFj
BIKOCX/CwcInKTYH5mp/4pE=
=hM6b
-----END PGP SIGNATURE-----