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

Site Navigation

PRs for manpage 'find(1)'

This is an experimental report containing PRs for manpage 'find(1)' as of Thu Apr 24 07:36:59 2014 UTC. See notes.


PRs for manpage 'find(1)':
SSubmittedTrackerResp.Description
p2014/01/01bin/185393jillesfind(1): -lname buffer read overflow bug
o2012/04/01docs/166553docfind(1): find -delete documentation is misleading
o2012/03/13bin/166056[patch][bin] find(1) fails with .: permission denied, even when using absolute paths
o2011/04/28bin/156703[patch] find(1) ignores whiteouts even with '-type w'
o2008/10/31bin/128493[patch] find(1) exits if -fstype test fails with EACCES
o2008/08/08bin/126384[request] find(1) doesn't support whiteout entries yet, but part of code already present
o2008/05/29bin/124084find(1): find -execdir does not prepend ./ to filenames, causing problems for certain files.
o2006/12/18bin/106872[patch] [request] extattr support for find(1)
o2004/06/14bin/67943find(1) fails when current directory is not readable by user
9 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.