how to get bazaar log rid of minor "sandbox" commits?

Rahul Nabar rpnabar at gmail.com
Thu Mar 12 01:27:45 GMT 2009


On Wed, Mar 11, 2009 at 7:41 PM, Ben Finney
<bignose+hates-spam at benfinney.id.au> wrote:
> It's not for one user of the repository (and remember that with a
> DVCS, any repository can, in future, gain extra users) to declare what
> existing history “does not matter”. If the data exists, and you have
> nothing to hide, it's best that it be available for later analysis if
> desired.

Thanks Ben! True. Didn't think of it since I am using Bazaar strictly
in a "single user" mode. No collaboration. Only revision history and
rollback capacity.

>
> If you want a way to make the history cleaner, that speaks to a
> requirement for a way for the user to view history ignoring some types
> of revision. This is very different from removing them from history
> completely.

Right; so what are the ways of imposing a heirarchy on revisions. Can
I have commits of the first order (major changes) and commits of the
second order (minor sandbox changes)  or some such paradigm? How does
one do that?

Does Bazaar or a related plugin allow me to do this?

-- 
Rahul



More information about the bazaar mailing list