1 |
On 18:04 Mon 31 May , Drake Wyrm wrote: |
2 |
> At 2004-05-31T19:32:31-0400, Chris Gianelloni <wolf31o2@g.o> wrote: |
3 |
> > On Mon, 2004-05-31 at 15:56, Mike Frysinger wrote: |
4 |
> > > On Monday 31 May 2004 03:24 pm, stan wrote: |
5 |
> > > > or masked and unmasked etc |
6 |
> > > > So that bugs against ~x86, ~ppc64 etc can be differentiated more easily |
7 |
> > > > from reports on packages that have been marked stable. |
8 |
> > > |
9 |
> > > i dont think it'd really be used all that often |
10 |
> > |
11 |
> > I would have to agree. Especially since most people don't use half the |
12 |
> > drop downs as it is... so much so that I barely even notice what is in |
13 |
> > them, since 95% of the time, it is simply the defaults and gives no |
14 |
> > information. I *will* look there before requesting that information |
15 |
> > from the user, but as I said, it tends to always be the defaults. |
16 |
> |
17 |
> Would it be the least bit helpful if non-devs who wish to help went |
18 |
> through incoming bug reports and made sure that all the relevant |
19 |
> information was there? |
20 |
> |
21 |
> -- |
22 |
> Batou: Hey, Major... You ever hear of "human rights"? |
23 |
> Kusanagi: I understand the concept, but I've never seen it in action. |
24 |
> --Ghost in the Shell |
25 |
|
26 |
It would be an incredibly dull task, but if people would like to help in that area, it would be greatly appreciated. Also, I don't buy the argument that because people don't use some of the options now (or they use it incorrectly) we should not implement helpful features. I think this would help bring up queries against bugs in the stable tree vs bugs in the "testing" tree. (If this can be done now, please inform me). I believe the major reason why people can not report bugs correctly is because of lack of documentation for it. In that respect, I am planning to write a Bug Reporting HOWTO (gentoo specific) in similar fashion to liquidx's Common Ebuild Mistakes document. |
27 |
|
28 |
Regards, |
29 |
Yi |