John A Meinel wrote:
> -r X -r Y is a lot more difficult to support (I'm not sure about our
> current parser, but the older parser wouldn't allow you to give the same
> option twice, I think the new one always picks the last supplied).
optparse supports this natively, so it's just a matter of hooking into
that support, if we choose to do this.
> It is marked as a wishlist, though something like this might be a great
> place for a plugin. Which could enable 'cvs compatibility mode' or
> somesuch.
What's interesting is that such a plugin would just need to replace the
definition for 'revision' in options.py
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel wrote:
> -r X -r Y is a lot more difficult to support (I'm not sure about our
> current parser, but the older parser wouldn't allow you to give the same
> option twice, I think the new one always picks the last supplied).
optparse supports this natively, so it's just a matter of hooking into
that support, if we choose to do this.
> It is marked as a wishlist, though something like this might be a great
> place for a plugin. Which could enable 'cvs compatibility mode' or
> somesuch.
What's interesting is that such a plugin would just need to replace the
definition for 'revision' in options.py
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFFLdTS0F+ nu1YWqI0RAmzxAJ 9s9BFGIJqLsZ2x5 BHI8KWhk1TH2gCf ZBKq xONhP+U0=
I6gfGkqTrpwZXyV
=skHF
-----END PGP SIGNATURE-----