bug#12658: [patches] some undocumented options in chcon

[Jim Meyering]

Benno Schulenberg wrote:
> The texi documentation of chcon does not mention the options
> --dereference, --preserve-root and --no-preserve-root, while the
> usage message just misses the latter two.  The third attached
> patch fixes this, plus a missing word in the general description
> of the --preserve options.
>
> The second attached patch removes a stray parenthesis in the
> documentation of cp.
>
> In the description of --force for cp, saying that -f is redundant
> when -n is specified makes it sound as if -n encompasses -f,
> whereas in fact -n cancels, nullifies, overrides -f.  So the first
> attached patch changes "redundant" to "ignored".
...

Hi Benno,

Thank you for the patches.  I've just applied this one (it affects
only coreutils.texi), but will defer the other two until after 8.20,
to give translators a chance to adapt to those --help changes.
Please ping us if they're not applied soon after 8.20.

> Subject: [PATCH 2/3] doc: remove a stray parenthesis from description of 'cp 
> --force'
>
> * doc/coreutils.texi (cp invocation): Remove Cheshire Cat.
> ---
>  doc/coreutils.texi |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/doc/coreutils.texi b/doc/coreutils.texi
> index d3e24fe..cac66a4 100644
> --- a/doc/coreutils.texi
> +++ b/doc/coreutils.texi
> @@ -7724,7 +7724,7 @@ Equivalent to @option{--no-dereference 
> --preserve=links}.
>  @opindex -f
>  @opindex --force
>  When copying without this option and an existing destination file cannot
> -be opened for writing, the copy fails.  However, with @option{--force}),
> +be opened for writing, the copy fails.  However, with @option{--force},
>  when a destination file cannot be opened, @command{cp} then removes it and
>  tries to open it again.  Contrast this behavior with that enabled by
>  @option{--link} and @option{--symbolic-link}, whereby the destination file