maks blog, Hacks, fun around free software.
Subscribe to a syndicated feed of my weblog,
brought to you by the wonders of RSS.
There's more than one way to view this weblog; try these flavours on
Other blogs in our institute or friends.
linux-2.6 bugs cleanup part 2
Random notes on effective bugs cleanup on a bigger scale:
Ignore the subject. In 90% of the cases it is badly formulated and provides no clue.
Be on a good mood or don't even start.
Use different overviews (bts, mbox, web, reportbug-ng, ..) to not miss the easy stuff right on start.
Read the last message first. A please close message on the tail or an upstream nack keeps you from reading the previous ones. Obviously as curious person i often violate that rule.
Have prepared standard answers on FAQ: Debian kernel patch acceptance guidelines, report issue to Linux upstream, debug initramfs.
Be bold: A big wontfix list won't help anyone. Close right away.
In the ping mail directly write To the submitter. A Cc to the bug report makes it more personal.
Tag any bug that is against an old version with moreinfo in the ping mail. Gives the submitter a clear indication that this bug needs an update.
Sometimes a close acts better as ping, reopen quickly and use the info.