GNU bug report logs -
#29315
info cp: documentation feedback
Previous Next
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
[Message part 1 (text/plain, inline)]
Your bug report
#29315: info cp: documentation feedback
which was filed against the coreutils package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 29315 <at> debbugs.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)]
[Message part 3 (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)]
[Message part 5 (message/rfc822, inline)]
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
This bug report was last modified 6 years and 282 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.