PRs for manpage 'man(1)'
This is an experimental report containing PRs for manpage 'man(1)' as of Fri May 25 07:40:52 2012 UTC. See notes.
PRs for manpage 'man(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/03/15 | bin/166130 | [patch] man(1): i can not read japanese manual on ja_JP.UTF-8 | |
| o | 2011/10/10 | bin/161475 | [patch] man(1), treat pipe & files w/o slash | |
| o | 2011/07/16 | docs/158973 | gordon | Update man(1) |
| s | 2005/05/02 | bin/80530 | man(1) should become Unicode aware | |
| p | 2005/04/06 | bin/79607 | obrien | [patch] man(1) grok and default to bzip2-compressed manual pages |
| p | 2002/01/25 | bin/34270 | man(1) -k could be used to execute any command. | |
| p | 1999/09/21 | bin/13869 | man(1) program saves multiple cached copies of the same file |
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.