any optparse branches floating around

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
| We just had #46432, where bzrtools accidentally overrides the
| description of another command's option.  I would like sometime to clean
| up the option code to make it less dependent on global definitions, e.g.
| in defining short names.

I don't think we'll see much more of that-- that part of bzrtools was
written when adding to OPTIONS was the only way to define new options.

| Before I do - does anyone have a patch/branch to use optparse instead of
| handcoded parsing?  There seemed to be a consensus this would be a good
| thing to do?

Not I.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEdZ6Y0F+nu1YWqI0RAuPeAJwNo9m14zoQtHHBDgUmHY+y5b5evgCfZV+U
1Nt/iZERbsv7O8XpMpooUN8=
=6Qhl
-----END PGP SIGNATURE-----