PRs for manpage 'route(8)'
This is an experimental report containing PRs for manpage 'route(8)' as of Sat Dec 7 07:38:51 2013 UTC. See notes.
PRs for manpage 'route(8)':
|o||2013/11/05||bin/183687||net||[patch] route(8): route add -net 172.20 add wrong host address|
|p||2013/08/25||bin/181532||glebius||[patch] route(8): 'route get' without destination gives misleading error message|
|o||2009/09/30||conf/139255||8.0-RC1 network.subr calls route(8) with obsolete parameter "cloning"|
|o||2009/02/04||bin/131365||net||route(8): route add changes interpretation of network specification [regression]|
|o||2008/05/06||bin/123465||net||[ip6] route(8): route add -inet6 <ipv6_addr> -interface gif0 -proxy mangle ipv6 address|
|o||2007/10/19||bin/117339||net||[patch] route(8): loading routing management commands from file|
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.