On 10/31/07, Nick Guenther wrote:
Why not start with the PR database? Pick a category and class that
appeals, do a search or two, and off you go with problems to solve.
The fact that they're in the PR database would seem to indicate that
fixing them would be useful for *someone*.
In my experience at my day job, good fixes for "janitor" issues can
often require a broad vision for all the interacting parts. If they
were simple nits, they would have been fixed on the spot. Instead,
they're still irksome because the solution isn't completely obvious.
(Maybe my definition for "janitor issue" doesn't match yours...)
Philip Guenther
| Justin C. Sherrill | Re: pkgsrc bulk build and tiff |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Ingo Molnar | [crash, bisected] Kernel BUG at ffffffff8079afb1 (__netif_schedule()) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Evgeniy Polyakov | Re: tbench wrt. loopback TSO |
