Am 05.08.10 15:40, schrieb Stephen Leake:
> We added a 'deprecate option' mechanism.
> 
> Deprecated options don't show up in help, even with --hidden.
> 
> So far, the only option we've deprecated is --full, replaced by
> --verbose. That's simple enough.
> 
> But I can imagine a case where someone needs to see the help for the
> deprecated option in order to figure out how to use the replacement
> option. 
> 
> So perhaps --hidden should show the deprecated options? or some new
> option --show-deprecated?

What about documenting the deprecated options and their replacements in
monotone.texi? Just showing them again won't help the user much and it
would just introduce new "meta" code we don't want to care about much.

> Similarly, we should have deprecated commands (not in this branch). For
> example, privkey, pubkey, read are apparently deprecated now.

I second the request to introduce that and it might become even more
needed when we hit 1.0, so we still provide backwards compatiblity. I
wouldn't go so far to deprecate privkey, pubkey and read though - these
are still used to backup / export / import keys or how do you want to
handle these otherwise? One might deprecate the reader functionality
packets other than keys though.

Thomas.

-- 
GPG-Key 0x160D1092 | [email protected] | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel

Reply via email to