Python plugins, third round

[Michael Ellerman]

On Thu, 16 Jun 2005 03:48 pm, John A Meinel wrote:
> Martin Pool wrote:
> >I'd also like --no-plugins, which would disable them altogether, and
> >sometimes be a better choice than 'bzr builtin'.
>
> So are you thinking that:
> bzr builtin command <= run the built-in form of command, but still load
> plugins
> bzr --no-plugins command <= don't load any plugins
>

That makes sense.

You might want to use the builtin form of a command but still use a 
non-standard branch class for example.

And it *might* be nice to have:

bzr --disable-plugin=foo command

to only disable one plugin. Although then you might need --enable-plugin, hmm.

cheers

-- 
Michael Ellerman
IBM OzLabs

email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050616/0a70c950/attachment.pgp