© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Sorry but I'll bother you with one additional comment and try to shut up.
On Fri, 28 Jan 2011, Alexander Belchenko wrote:
> Bazaar has no CLI-way to explore arbitrary revision metadata even for regular branches, not only
> for merge directives. So if somebody want to harm the project in the way you have described then
> it's possible to do even today with regular branches.
Looks that way... In my opinion there should be an easy way to fully audit whatever is in the repository and whatever goes in. All bits of it, not just some part of it.
I have spent 10 years of my life watching over a sensitive CVS repository to make sure that nothing bad happens to it. My work uniform was a tinfoil hat and I still have the same mentality as you can see :). CVS repo is easy to audit. Bazaar repo is not. We probably could have not adopted Bazaar in that environment because of this reason.