[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if
bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not
Fri, 11 Jan 2019 02:17:33 -0700
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
severity 15727 wishlist
retitle 15727 doc: cp: expand dirs-vs-files with -f/--remove-dest
On 2013-10-29 12:20 p.m., Linda Walsh wrote:
You need to make the docs much more clear about "cp"s limitations.
update isn't eally update, and -T is certainly wrong at the very
least. If you feel you'd rather document cp's limitations,
cp is a great tool, don't get me wrong! But when it added update
and -T, --remove-destination, it started inferring or promising
more than you were willing to deliver. That should be documented.
Based on the above (as the result of the long discussion),
I'm marking this as a documentation wish-list item:
clarify that "-f" and "--remove-destination" won't replace a file
with a directory (as explained by Pádraig and Bernhard in the thread).
Similarly for related limitations of "-T".
|[Prev in Thread]
||[Next in Thread]|
- bug#15727: Bug: cp <-a|-archive> (w/<-f|--remove-destination>) breaks if one of files is a dir and other not,
Assaf Gordon <=