From: Adrian Bunk <bunk@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>
Subject: Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup)
Date: Mon, 26 Nov 2007 22:45:55 +0100 [thread overview]
Message-ID: <20071126214554.GD917@stusta.de> (raw)
In-Reply-To: <200711260130.06985.rjw@sisk.pl>
On Mon, Nov 26, 2007 at 01:30:06AM +0100, Rafael J. Wysocki wrote:
> On Monday, 26 of November 2007, Adrian Bunk wrote:
>...
> > That's not possible, but as already said it's not required.
> > And more important, it's unrelated to any problems we have.
> >
> > And it sounds funny that you first write specifications mandating stuff
> > like "IMO, first, it should ask for what the bug is against" and then
> > demand an additional email interface that bypasses everything you
> > demanded previously.
>
> I just realize that there are people who wouldn't like to use the web interface
> and would prefer to use email instead.
In the cases where these are kernel developers that do (or should)
handle dozens of bugs each week I see a point if they have problems
integrating some medium into their workflow.
But in all software, no matter whether open source or commercial, bug
reporters simply have to use whatever the vendor offers as support
channel.
> Moreover, you won't force people to use the web interface only for reporting
> bugs, because frankly for some kinds of problems it's too heavywieght
That developers who know what they are doing might bypass the bug
tracking is not a problem.
> (compilation problems and purely software, reproducible things like that are
> much faster resolved using email; this also applies to easily reproducible bugs
> in general). Still, it wouldn't hurt if they were automatically tracked.
This sounds like "a bit pregnant"...
Tracking requires things like e.g. categorizing the issue and marking it
as fixed when it got fixed.
> > > Also, if you "switch to email", and then want to switch back to the web
> > > interface, the Cc list from the email messages will be lost.
> >
> > The perfect is the enemy of the good.
>
> Sure.
>
> Greetings,
> Rafael
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-11-26 21:46 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
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 [this message]
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=20071126214554.GD917@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
/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