PRs for tag 'libalias'
This is an experimental report containing PRs for tag 'libalias' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'libalias':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2013/11/30 | kern/184389 | net | [libalias] libalias fails to adjust MTU from jails |
o | 2006/11/15 | kern/105579 | [libalias] dcc resume over natd in 6.x | |
o | 2004/11/27 | kern/74450 | [libalias] [patch] enable libalias/natd to create skipto rules when punching ipfw | |
o | 2003/07/27 | kern/54891 | [libalias] [patch] libalias(3)/natd(8) and exporting connection-info for identd | |
o | 2003/03/26 | kern/50310 | [libalias] [patch] natd / libalias fix to allow dcc resume in irc | |
o | 2002/08/04 | kern/41307 | [libalias] [patch] logging of links lifecycle (add/delete/change) |
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.