Re: Plugins not working under Mozilla 1.2b / Galeon 1.3 under RH73
mike <[email protected]>
| Newsgroups | gmane.comp.web.galeon.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2002-11-07 at 00:06, Christian Rose wrote: > tor 2002-11-07 klockan 00.32 skrev mike: > > > > (see > > > > http://bugzilla.gnome.org/show_bug.cgi?id=97769) > > > > > > I don't see how one user's unfounded ranting in a particular bug report, > > > that was misplaced to begin with, relates to this or bug reporting in > > > general. It was a funny read though. Or sad, to be honest. > > > > In just what way is it "unfounded ranting" > > It was accusatory and full of totally misplaced attempts at sarcasm, > which has absolutely no place in any bug report. Bug reports should be > neutral and concise explanations of the problem. Emotions have no place > in bug reports. If more information is needed, more information should > be provided in the same civilized manner. This report was the exact > opposite of that. It was accusatory this was my response which started off the rants So this bug gets closed because it only affects galeon with no investigation? genuine question 1. It does not affect "random plugins" - it affects all plugins 2. It does not happen on gnome-2.0.2/gtk-2.0.6 - only 2.1+ clarifying the situation So this means that bug wont be fixed? question again (BTW - I very raely use plugins myself - but if this is not fixed galeon2 will be unusable in gnome-2.2) How is this wrong > > > 1. The bug was posted against galeon (not gtk) > > Don't know why that should be of any significance for the rantings. > > > > 2. The bug was closed as a reflex action with no attempt to look at the > > issues > > That's your interpretation. There may be other reasons that you've > overlooked. Some configurations aren't supported because they cannot be > supported, because they involve several other pieces of code that may > also be unstable at the same time, making troubleshooting very difficult > and possibly also pointless since both pieces of software may be under > heavy development and the problem may be very temporary. Maybe the > author already knows that this piece of code is buggy and is not > interested in bug reports at this point in time. And so on. > > To me, it's more likely your responses that seem reflex-like and jumping > the gun. Don't take a bug report closed with any resolution you didn't > expect as a personal attack. But it seems you did just that. > > > > Also please xplain your definition of "misplaced", obviously my english > > education was lacking somewhere. > > Accusations and sarcasm have no place in a bug report. > > > > So your view is that bugs should not be reported if any excuse can be > > made to the effect of "not me guv" > > Not at all. Bugs should be reported. But likewise, the developer's > decision should be respected. If you don't agree with the resolution of > the bug report, then provide more details in a civilized manner. Simple > as that. > > > Christian > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Galeon-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/galeon-devel -- Linux, Gnome what more do you need http://www.redtux.demon.co.uk ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en