From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Frans Pop <elendil@planet.nl>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: "buggy cmd640" message followed by soft lockup
Date: Sat, 24 Nov 2007 20:07:51 +0100 [thread overview]
Message-ID: <200711242007.52430.rjw@sisk.pl> (raw)
In-Reply-To: <200711241904.13132.bzolnier@gmail.com>
On Saturday, 24 of November 2007, Bartlomiej Zolnierkiewicz wrote:
[--snip--]
> Rafael, I see that you've filled a bug for this bugreport into kernel
> bugzilla tracker (one day after the bugreport):
>
> http://bugzilla.kernel.org/show_bug.cgi?id=9442
>
> Since we try to address regressions with the highest priority in the
> IDE-land (and usually they get fixed quickly) I would strongly prefer to
> use bugzilla only for long-term bugs and avoid the needless bureaucracy.
As a rule, I put all of the reported regressions into the Bugzilla early. You
are not required to use these entries for tracking the bugs, though. If you
don't want to, just leave the entry as is and I'll close it when the fix is in
the Linus' tree.
> Therefore I kindly ask you to defer filling bugs for new bugreports for
> a week or two, and give us some time to react (and always ping me about
> the bugreport status before filling bugzilla entry).
Well, I thought you'd get an email from the Bugzilla, but of course I can notify
you directly about reported regressions related to IDE.
> The alternative solution would be that you fill all new bugreports but
> then please assign them to yourself and track their status (if after two
> weeks the problem is not fixed feel free to reassign bug to me).
I can do that, but please note that the bugs filed against IDE are assigned to
you automatically, so I'll have to reassign them to me (as I've just done with
this particular entry). If you don't want them to be assigned to you at all,
please contact the Bugzilla administrators and ask them to change that.
Thanks,
Rafael
next prev parent reply other threads:[~2007-11-24 18:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 19:07 "buggy cmd640" message followed by soft lockup Frans Pop
[not found] ` <200711241904.13132.bzolnier@gmail.com>
2007-11-24 19:07 ` Rafael J. Wysocki [this message]
2007-11-25 0:26 ` kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup) Bartlomiej Zolnierkiewicz
2007-11-25 13:11 ` Rafael J. Wysocki
2007-11-25 13:49 ` Adrian Bunk
2007-11-25 20:07 ` Rafael J. Wysocki
2007-11-25 20:08 ` Dr. David Alan Gilbert
2007-11-25 20:32 ` Adrian Bunk
2007-11-25 21:28 ` Rafael J. Wysocki
2007-11-25 21:36 ` Adrian Bunk
2007-11-25 22:38 ` Rafael J. Wysocki
2007-11-25 22:40 ` Adrian Bunk
2007-11-25 23:28 ` Rafael J. Wysocki
2007-11-25 23:34 ` Adrian Bunk
2007-11-26 0:30 ` Rafael J. Wysocki
2007-11-26 21:45 ` Adrian Bunk
2007-11-26 22:57 ` Rafael J. Wysocki
2007-11-25 22:55 ` Rafael J. Wysocki
2007-11-25 14:08 ` Bartlomiej Zolnierkiewicz
2007-11-25 20:25 ` Rafael J. Wysocki
[not found] ` <200711242038.06677.elendil@planet.nl>
2007-11-24 20:12 ` "buggy cmd640" message followed by soft lockup Rafael J. Wysocki
[not found] ` <200711250013.51279.bzolnier@gmail.com>
2007-11-26 1:32 ` Frans Pop
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=200711242007.52430.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-ide@vger.kernel.org \
--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