PRs for manpage 'kbdcontrol(1)'
This is an experimental report containing PRs for manpage 'kbdcontrol(1)' as of Fri May 30 07:37:36 2014 UTC. See notes.
PRs for manpage 'kbdcontrol(1)':
|o||2014/02/25||bin/187069||kbdcontrol(1) will not define "F" keys on console F1-F12 [regression]|
|o||2013/07/22||bin/180740||kbdcontrol(1) cannot override function keys for console [regression]|
|o||2013/07/12||bin/180497||kbdcontrol(1) cannot override function keys < 65|
|o||2013/01/19||bin/175425||[patch] kbdcontrol(1) printout about kbdmux isn't informative|
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.