how to get bazaar log rid of minor "sandbox" commits?
Martin Pool
mbp at sourcefrog.net
Thu Mar 12 02:02:30 GMT 2009
2009/3/12 Rahul Nabar <rpnabar at gmail.com>:
>> 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?
The easiest way for you to implement it is perhaps to use a convention
in your commit messages, and then you can for example use 'bzr log
--message' to find them again. For instance I sometimes commit with
'[broken]' at the start of the message when I know I'm committing with
failing tests, which sounds a bit like the case you started from.
There's also some discussion in another thread of a more powerful
predicate language here.
If you want something more structured we could look at tagging
revisions with properties; if you can come up with a taxonomy that
would be generally useful it might be supported in both commit and log
etc. But I suspect it's going to be a bit user- or project-specific.
--
Martin <http://launchpad.net/~mbp/>
More information about the bazaar
mailing list