GNU bug report logs - #29315
info cp: documentation feedback

Previous Next

Package: coreutils;

Reported by: kalle <kalle <at> projektwerkstatt.de>

Date: Thu, 16 Nov 2017 10:37:02 UTC

Severity: normal

Done: Pádraig Brady <P <at> draigBrady.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Pádraig Brady <P <at> draigBrady.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#29315: closed (info cp: documentation feedback)
Date: Sun, 10 Dec 2017 00:24:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sat, 9 Dec 2017 16:23:24 -0800
with message-id <1acbe31b-7d4d-e4bf-d117-1a3c361c7962 <at> draigBrady.com>
and subject line Re: bug#29315: info cp: documentation feedback
has caused the debbugs.gnu.org bug report #29315,
regarding info cp: documentation feedback
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
29315: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29315
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: kalle <kalle <at> projektwerkstatt.de>
To: bug-coreutils <at> gnu.org
Subject: info cp: documentation feedback
Date: Thu, 16 Nov 2017 12:36:06 +0100
hello,
here some mistakes/improvement proposals to `info cp' from me:

-sentence "If the `--target": take away "failing that"?
-sentence "descending into source directories": shouldn't it be rather
"descending into SOURCE's directories"?And since `-r' and `-R' is the
same: write "-r/-R" instead.
-option `-f': why is it written about _opening_ a file, e.g. "opened for
writing" and not simply "writeable"? What is meant by "removes it and
tries to open it again"? It is said "`cp' then removes it". It should be
added ", if the user has write-permission in the containing directory."
-part "-i": shouldn't be written "When copying to a file" instead?

greetings,
kalle


[Message part 3 (message/rfc822, inline)]
From: Pádraig Brady <P <at> draigBrady.com>
To: kalle <kalle <at> projektwerkstatt.de>, 29315-done <at> debbugs.gnu.org
Subject: Re: bug#29315: info cp: documentation feedback
Date: Sat, 9 Dec 2017 16:23:24 -0800
[Message part 4 (text/plain, inline)]
On 16/11/17 03:36, kalle wrote:
> hello,
> here some mistakes/improvement proposals to `info cp' from me:
>
> -sentence "If the `--target": take away "failing that"?

It's better as is, to document that these are separate modes

> -sentence "descending into source directories": shouldn't it be rather
> "descending into SOURCE's directories"?

That could be interpreted as only descending one level

> And since `-r' and `-R' is the
> same: write "-r/-R" instead.

That would be less standard/searchable

> -option `-f': why is it written about _opening_ a file, e.g. "opened for
> writing" and not simply "writeable"?

There can be differing restrictions on various operations,
so we're being explicit about the truncation permission.

> What is meant by "removes it and
> tries to open it again"?

It creates a new file rather than rewriting an existing one.
I suppose that could be clarified. Patch attached.

> It is said "`cp' then removes it". It should be
> added ", if the user has write-permission in the containing directory."

There are other permissions that may block the unlink also.
It's better not to partially list potential issues,
and just state what cp does.

> -part "-i": shouldn't be written "When copying to a file" instead?

Subtly no, because we prompt if overwriting a dir with a file.
So the prompt depends on the source, not the dest.

cheers,
Pádraig.
[cp-f-recreate.patch (text/x-patch, attachment)]

This bug report was last modified 6 years and 337 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.