[commit] Doc: -var-delete

[Eli Zaretskii]

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Mon, 4 Dec 2006 17:41:03 +1300
> Cc: gdb-patches@sources.redhat.com
> 
> I was trying to apply the definition in MAINTAINERS:
> 
>   An "obvious fix" means that there is no possibility that anyone will
>   disagree with the change.
> 
> As I'm documenting existing (undocumented) functionality I can't see how anyone
> can disagree.

The _need_ for documenting an existing feature is indisputable (at
least in this case, since that is my policy; you know as well as I do
that, in the case of Emacs, for example, RMS has a different policy,
so even the need for documenting an existing feature does not
necessarily constitute a good-enough reason).  However, _how_ it
should be documented is not obvious in any way; I could express the
same idea as you did in about a dozen different ways.

> Why do you think it is not obvious?

Because about the only kind of fix in the docs that is really obvious
is a typo or bad English.