PRs for manpage 'ls(1)'
This is an experimental report containing PRs for manpage 'ls(1)' as of Fri May 30 07:37:55 2014 UTC. See notes.
PRs for manpage 'ls(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/04/27 | bin/189057 | [PATCH] Adding an option to ls(1) to display file permissions in octal | |
| o | 2010/11/04 | kern/151942 | fs | [zfs] [panic] panic during ls(1) zfs snapshot directory |
| o | 2009/11/10 | docs/140435 | ls(1), section STANDARD: the -A is exception from POSIX also | |
| o | 2007/09/17 | bin/116425 | [patch] [request] ls(1) options for pre-sort of directories first or last, & listing of directories or non-directories explicitly | |
| a | 2007/05/12 | bin/112613 | vwe | ls(1): 'ls -l' is very slow or doesn't work at all |
| o | 2004/08/22 | standards/70813 | standards | [patch] ls(1) not Posix compliant |
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.