PRs for manpage 'rm(1)'
This is an experimental report containing PRs for manpage 'rm(1)' as of Fri May 30 07:39:05 2014 UTC. See notes.
PRs for manpage 'rm(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/03/27 | bin/188008 | [patch] rm(1): Better(?) rm -If behavior (and other combination between -I, -i, and -f) | |
| o | 2008/08/10 | bin/126433 | [patch] some missing checks in rm(1) | |
| o | 2007/09/19 | standards/116477 | standards | rm(1): rm behaves unexpectedly when using -r and relative paths |
| o | 2005/01/26 | bin/76711 | [patch] rm(1): parse error in rm.c:check() while parsing value returned from strmode(3) |
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.