A question about uncommit

[Martin Pool]

On  8 May 2006, Wayne Davison <wayned at samba.org> wrote:
> I had a reason to do an uncommit today, and ended up having some
> questions.  First, I noticed that the uncommit does not actually
> remove the data from the committed changes, just some "pointer"
> files -- i.e. the ID in branch/revision-history changed, the XML
> inventory in checkout/basis-inventory changed, and the ID in
> checkout/last-revision changed, but nothing else.  There is an
> option listed for the uncommit sub-command that looks like it was
> supposed to change this, but it doesn't work (--all is rejected).
> 
> FYI, I'm using a freshly-created knit branch created by bzr 0.8.
> 
> So, is this supposed to work this way?  In looking around, it would
> seem the answer to this is "yes".  If so, is there a command planned
> to clean out any old, useless revision data?  Perhaps something like
> John's old clean-weave plugin (but presumably merged into bzr)?

Ideally we would remove them but the current code does not try to.  This
probably should not be the default behaviour because the revision data
might be used by something else in the repository, but an option should
be fine.

  https://launchpad.net/products/bzr/+bug/43753

> Bonus: since "uncommit --all" does not work anymore, attached is a
> patch to remove the mention of the --all option.

Thanks, taken.

-- 
Martin