Suggestion: Remove baz importers from bzrtools
aaron.bentley at utoronto.ca
Wed Aug 30 17:44:25 BST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Kevin Smith wrote:
> Every time I do bzr help commands, I am annoyed at having to ignore two
> commands, near the top of the list, that I will never use.
bzrtools is a bit of a swiss-army knife. I've considered breaking it
into smaller pieces, but that will be pretty painful until nested-tree
support is implemented.
I'd be surprised though, if you use more than a fraction of what
The raison d'être of bzrtools is to be a one-stop shop for all the
add-on functionality that you're likely to want. I suppose there are
some subgroups here:
Foreign data support:
But most of it falls under "misc" heading, which makes it hard to describe.
I don't really know whether there's a reason to single out the baz
importers. There's a pretty strong counterargument: that bzr is the
successor to baz, designed to losslessly import its data, and in a
perfect world, baz-import would be in the core. (It's not, because that
would make the core depend on baz)
I suppose the other way to make baz-import go away would be to register
it as an upgrade mechanism, so that 'bzr upgrade' could transform a
bazaar archive into a bzr repository. That would get rid of the
command, but I'm not sure that's the right approach, and it would still
leave 'baz-import-branch', because upgrade doesn't really handle that case.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar