[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Reporting bugs upstream



Dave Jones <davej redhat com> wrote:
> On Fri, Jan 20, 2006 at 08:52:18PM -0300, Horst von Brand wrote:
>  > Mike A. Harris <mharris mharris ca> wrote:
>  > 
>  > [...]
>  > 
>  > > Sure, the system isn't perfect.  And the situation you describe is
>  > > entirely feasible.  However, I've seen bugs reported in which it is
>  > > perfectly clear that a user has never even attempted to see if there
>  > > was a duplicate, because their subject line or other aspects of their
>  > > bug were almost word for word identical to one or more other bug
>  > > reports, etc.

>  > It would be quite useful to show bugs (perhaps the most recent ones?) for
>  > the selected component. As things stand, you have to go search (select
>  > package, etc; and the search isn't very intuitive as it stands) and if not
>  > found, file a bug (again, select package etc). For me at least (far
>  > away in network terms) this is slow and somewhat irritating.

> You can save a query once you're logged in, and it appears as a
> pseudo-bookmark at the bottom of each bugzilla page.  I create one for
> kernel for each release, and use it countless times per day. I only ever
> use search if I'm looking for something in particular, like 'bugs
> pertaining to snd-nm256'.

That last one is my usual case, tripping over bugs in random packages.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]