| 1 |
On 03/08/10 18:08, Mark Loeser wrote: |
| 2 |
> What is this even in reference to? Its not at all clear what you are |
| 3 |
> trying to do. |
| 4 |
|
| 5 |
Okay, sorry. |
| 6 |
|
| 7 |
I was wondering what classes of bugs there are that are |
| 8 |
|
| 9 |
- reoccuring (therefore beloning to a "class" or "pattern") |
| 10 |
|
| 11 |
- relatively easy to fix |
| 12 |
|
| 13 |
- ideally suited for non-maintainer updates, |
| 14 |
i.e. stuff where the original maintainer just won't mind |
| 15 |
that you touched "his" ebuild, even if he feels more or less |
| 16 |
like its owner |
| 17 |
|
| 18 |
From such patterns I expect: |
| 19 |
|
| 20 |
- to find candidates more easy when I myself want to fix something |
| 21 |
within limited time |
| 22 |
|
| 23 |
- raising awareness on these bugs in hope other feel motivated |
| 24 |
to look outr and fix for some of those, too. |
| 25 |
|
| 26 |
- use these patterns to find future bugday candidates |
| 27 |
|
| 28 |
A bit clearer now? |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
Sebastian |
Archives