Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'cp(1)'

This is an experimental report containing PRs for manpage 'cp(1)' as of Wed Apr 23 07:36:33 2014 UTC. See notes.


PRs for manpage 'cp(1)':
SSubmittedTrackerResp.Description
o2013/07/21kern/180724occasional file corruption when using cp(1)
o2013/04/16bin/177885[patch] cp(1): regression on cp performance
a2013/02/14bin/176136markj[patch] cp(1) fails to overwrite a symlink pointing to a directory
a2012/12/16bin/174489markjcp(1): 'cp -a -n' fails when 'over-writing' a broken symlink
o2012/06/11docs/168962traszcp(1) & mv(1) pages don't mention ACLs or extended attributes
o2012/06/11bin/168961cp(1): cp should provide an option to copy file ACLs and attributes
o2010/03/07bin/144531[patch] cp(1) show percentage complete
o2009/01/23kern/130920fs[msdosfs] cp(1) takes 100% CPU time while copying file from harddisk to pendrive
o2005/10/21bin/87792[patch] very bad performance of cp(1) via NFS, possibly mmap() problem
o2003/06/19bin/53475cp(1) copies files in reverse order to destination
o2001/02/11bin/25015cp(1) options -i and -f do not work as documented
11 problems total.


Notes

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.