From: Jesper Juhl <jesper.juhl@gmail.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug reports ignored?
Date: Thu, 5 Jan 2006 17:52:23 +0100 [thread overview]
Message-ID: <9a8748490601050852t1e10ea6evd8769f2f4719186c@mail.gmail.com> (raw)
In-Reply-To: <38150.145.117.21.143.1136477335.squirrel@145.117.21.143>
On 1/5/06, Folkert van Heusden <folkert@vanheusden.com> wrote:
> Hi,
>
> Last couple of weeks I sent 2 bug-reports. They seem to be ignored. I was
> wondering: what is missing in them? Am I sending them to the incorrect
> address? One I also put into bugzilla (no reactions either).
>
Perhaps you could let us know the subjects & dates of those two
previous mails so they are easier to locate in the archives?
Speaking of bug-reports in general I believe the following holds pretty well :
- Sometimes bug-reports simply get lost in the flood of emails. This
is especially true if they are only send to lkml and not Cc'ed to the
proper maintainers/authors of the code involved. A well researched
list of recipients (including LKML) greatly increases the chance of a
reply.
- Sometimes bug-reports don't contain enough info to be able to say
anything useful. People are less inclined to respond to bug reports
like that since it often ends up with developers having to play "20
questions".
- Sometimes bugs are reported for Tainted kernels, these often just
get ignored. Reproduce the problem with an un-tainted kernel and
people will be more inclined to listen.
- Sometimes bugs are reported with a *demand* that it be fixed *right
now* or with other abusive language towards developers in the email.
Such reports are usually ignored or, if responded to, don't get very
positive replies.
Then there's also the situation where a lot of people actually do see
the report but don't feel they have anything useful to say on the
issue since it's outside their area of expertiese - a better Cc list
often helps :)
Most of the time I think it's just a case of too much mail and things
get missed unintentionally. Try again, possibly with a better
researched list of recipients and more details about the problem -
eventually the right people will notice :)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-01-05 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 16:08 Folkert van Heusden
2006-01-05 16:52 ` Jesper Juhl [this message]
2006-01-05 18:53 ` Folkert van Heusden
2006-01-05 21:17 ` Willy Tarreau
2006-01-05 21:41 ` Folkert van Heusden
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=9a8748490601050852t1e10ea6evd8769f2f4719186c@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®