PRs for manpage 'moused(8)'
This is an experimental report containing PRs for manpage 'moused(8)' as of Fri May 30 07:38:12 2014 UTC. See notes.
PRs for manpage 'moused(8)':
|o||2013/01/25||bin/175556||[PATCH] moused(8) virtual scrolling on alternate buttons|
|o||2012/10/26||bin/173133||[suspend/resume] moused(8) sometimes fails to reinitialise after suspend|
|o||2011/09/02||bin/160386||[patch] invert Z axis movement via moused(8)|
|o||2008/05/21||kern/123855||philip||moused(8): spontaneous mouse events|
|o||2006/04/13||bin/95698||philip||[patch] moused(8): Software control of sysmouse|
|o||2005/03/30||bin/79376||moused(8) causes random mouse events with a PS/2 mouse on FreeBSD-4.11|
|o||2004/12/17||bin/75177||philip||Bug selecting psm operation level in moused(8)|
|o||2003/01/04||bin/46758||[patch] moused(8) enhancements|
|o||2002/03/20||bin/36143||[patch] moused(8): add dynamic (non linear) mouse acceleration|
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.