PRs for manpage 'cp(1)'
This is an experimental report containing PRs for manpage 'cp(1)' as of Thu Apr 17 07:36:31 2014 UTC. See notes.
PRs for manpage 'cp(1)':
|o||2013/07/21||kern/180724||occasional file corruption when using cp(1)|
|o||2013/04/16||bin/177885||[patch] cp(1): regression on cp performance|
|a||2013/02/14||bin/176136||markj||[patch] cp(1) fails to overwrite a symlink pointing to a directory|
|a||2012/12/16||bin/174489||markj||cp(1): 'cp -a -n' fails when 'over-writing' a broken symlink|
|o||2012/06/11||docs/168962||trasz||cp(1) & mv(1) pages don't mention ACLs or extended attributes|
|o||2012/06/11||bin/168961||cp(1): cp should provide an option to copy file ACLs and attributes|
|o||2010/03/07||bin/144531||[patch] cp(1) show percentage complete|
|o||2009/01/23||kern/130920||fs||[msdosfs] cp(1) takes 100% CPU time while copying file from harddisk to pendrive|
|o||2005/10/21||bin/87792||[patch] very bad performance of cp(1) via NFS, possibly mmap() problem|
|o||2003/06/19||bin/53475||cp(1) copies files in reverse order to destination|
|o||2001/02/11||bin/25015||cp(1) options -i and -f do not work as documented|
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.