PRs for manpage 'find(1)'
This is an experimental report containing PRs for manpage 'find(1)' as of Fri May 30 07:37:01 2014 UTC. See notes.
PRs for manpage 'find(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| p | 2014/01/01 | bin/185393 | jilles | find(1): -lname buffer read overflow bug |
| o | 2012/04/01 | docs/166553 | doc | find(1): find -delete documentation is misleading |
| o | 2012/03/13 | bin/166056 | [patch][bin] find(1) fails with .: permission denied, even when using absolute paths | |
| o | 2011/04/28 | bin/156703 | [patch] find(1) ignores whiteouts even with '-type w' | |
| o | 2008/10/31 | bin/128493 | [patch] find(1) exits if -fstype test fails with EACCES | |
| o | 2008/08/08 | bin/126384 | [request] find(1) doesn't support whiteout entries yet, but part of code already present | |
| o | 2008/05/29 | bin/124084 | find(1): find -execdir does not prepend ./ to filenames, causing problems for certain files. | |
| o | 2006/12/18 | bin/106872 | [patch] [request] extattr support for find(1) | |
| o | 2004/06/14 | bin/67943 | find(1) fails when current directory is not readable by user |
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.