Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs considered easy by the bugbusting team

This is an experimental report from the bugbusting team containing PRs that we think are "easy" as of 4-16-2014. If you're a committer interested in helping us with the backlog, this is a great place to start. It is generated from a file on freefall once per day.

This is intended to be a highly-filtered list to see if we can get more people interested in bugbusting without being overwhelmed by the large number of PRs.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.

SSubmittedTrackerResp.Description
o2010/08/23kern/149917qingli[net] [patch] freebsd 8.1 crash with ECMP
o2008/05/05bin/123418[patch] du(1): add -g (Gbyte) option to du(1) + manpage cleanup
2 problems total.

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.