Re: [Monotone-devel] nvm.options

[Stephen Leake]

Thomas Keller <address@hidden> writes:

> Am 21.07.10 12:18, schrieb Stephen Leake:
>> We need a NEWS entry, and something in monotone.texi. How about this:
>> 
>> NEWS
>>         New Features
>> 
>>         - Options can now be overridden; you can specify --no-unknown
>>           --unknown on the command line. Similarly, you can specify
>>           --no-unknown in the get_default_command_options hook, then
>>           change it to --unknown on the command line.
>
> As I mentioned in my earlier mail the NEWS entry should include more
> details what options got hidden, deprecated, replaced and / or removed
> exactly. Yes, this is also a tedious task, but given the fact that not
> mentioning it might lead to weird user experiences, especially if the
> information is also nowhere available else, its a must.

Ok. I'll work on this.

> Since we have quite a few things now which we at least plan to remove in
> 2.0, I start to think that adding a dedicated manual section for that
> purpose is a good idea. What do others think about that?

Yes, that makes sense.

>> We could modify the description of _every_ command that now has a
>> resettable option. Tedious, but do-able. But perhaps we should consider
>> generating the command options from the help texts, automatically? This
>> would be a modification of the 'mtn manpage' command. That way the info
>> manual would be as complete as the online help.
>> 
>> Or maybe it's ok as is.
>
> Actually not quite, e.g. "mtn serve" currently lists two hidden options,
> --stdio and --no-transport-auth, so again I think we have to go over all
> these sections and tweak them accordingly, 

I'll work on this.

> if nobody steps up and finds a good way to include at least the
> command calling syntax from the main program.

I think that's doable, and a good idea, but probably more work than I
want to sign up for right now.

-- 
-- Stephe