public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@cs.kun.nl>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity
Date: Wed, 24 Jul 2002 20:31:00 +0200	[thread overview]
Message-ID: <200207242031.00486.pauldv@cs.kun.nl> (raw)
In-Reply-To: <200207240647.14935.jsmith@kcco.com>

On Wednesday 24 July 2002 13:47, Jean-Michel Smith wrote:
> It may take a couple or three weeks, but the bug reports do get read,
> assigned, and fixed.  Of course, if the reports are just sent to the list
> and complained about, but never filed with bugzilla, it is entirely
> possible they'll never get fixed.  The developers have made it plain on
> more than one occasion that the mailing lists and forums are in general a
> bad place to be filing bug reports.
>

I submitted enough bug reports, and they the fixing time tends to vary. The 
main reason for slow fixes is either "there is no known solution" (just a 
difficult bug), "the bug report sucks" (what the hell goes wrong, the ebuild 
is not good enough and needs a lot of work), "upstream is slow" (well, we 
cannot fix it, but are waiting for upstream). Ebuild patches are generally 
processed fast, especially if you describe what your patch does and why. This 
is to a degree also true for program patches.

In short, the more you do, the faster you will get a result.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net



      reply	other threads:[~2002-07-24 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 22:53 [gentoo-dev] Bugs Bugs Bugs & Unstablity Doug Goldstein
2002-07-23 23:08 ` Stefano Peluchetti
2002-07-24  7:16 ` Vitaly Kushneriuk
2002-07-24  8:13 ` Kim Nielsen
2002-07-24 11:47   ` Jean-Michel Smith
2002-07-24 18:31     ` Paul de Vrieze [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207242031.00486.pauldv@cs.kun.nl \
    --to=pauldv@cs.kun.nl \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox