From: "François Valenduc" <francois.valenduc@tvcablenet.be>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugme-daemon@bugzilla.kernel.org, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: [Bugme-new] [Bug 11144] New: dhcp doesn't work with iwl4965
Date: Wed, 23 Jul 2008 11:17:27 +0200 [thread overview]
Message-ID: <4886F727.6010301@tvcablenet.be> (raw)
In-Reply-To: <20080723010522.389a948f.akpm@linux-foundation.org>
Andrew Morton a =E9crit :
> On Wed, 23 Jul 2008 09:58:21 +0200 Fran__ois Valenduc <francois.valen=
duc@tvcablenet.be> wrote:
>
> =20
>> P.S: why don't you want to use the bugzilla interface ?
>> =20
>
> Depends on the subsystem. ACPI is 100% bugzilla-based, net people=20
> prefer email, others are in-between.
>
> Plus for recently-occurring bugs it's best to knock them over via ema=
il
> without getting into bugzilla bureaucracy. bugzilla is more
> appropriate to longer-term bugs.
>
> And when the bug affects multiple subsystems, multiple
> developers and we don't even know which subsystem introduced it, it i=
s
> much better to perform the diagnosis and repair via email.
>
>
> I make a judgement call on each report. Been doing it for a while,
> don't get too many complaints ;)
>
>
> =20
OK, thanks for the explanation. But do you have more ideas about the=20
problem ?
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-23 9:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11144-10286@http.bugzilla.kernel.org/>
2008-07-22 10:48 ` [Bugme-new] [Bug 11144] New: dhcp doesn't work with iwl4965 Andrew Morton
2008-07-22 10:52 ` Patrick McHardy
2008-07-23 7:58 ` François Valenduc
2008-07-23 7:59 ` François Valenduc
2008-07-23 8:05 ` Andrew Morton
2008-07-23 9:17 ` François Valenduc [this message]
2008-07-23 10:12 ` Patrick McHardy
2008-07-23 11:29 ` François Valenduc
2008-07-23 11:31 ` Patrick McHardy
2008-07-23 11:58 ` François Valenduc
2008-07-23 12:36 ` François Valenduc
2008-07-23 12:44 ` Patrick McHardy
2008-07-23 12:51 ` Patrick McHardy
2008-07-23 14:57 ` François Valenduc
2008-07-23 15:18 ` Patrick McHardy
2008-07-23 15:19 ` Patrick McHardy
2008-07-23 15:42 ` François Valenduc
2008-07-23 15:52 ` Patrick McHardy
2008-07-23 15:58 ` François Valenduc
2008-07-23 15:59 ` Patrick McHardy
2008-07-23 16:25 ` Patrick McHardy
2008-07-23 21:21 ` David Miller
2008-07-24 8:58 ` Patrick McHardy
2008-07-24 10:17 ` Tomas Winkler
2008-07-24 10:19 ` Patrick McHardy
2008-07-24 11:35 ` Tomas Winkler
2008-07-24 11:45 ` Johannes Berg
2008-07-30 18:04 ` François Valenduc
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=4886F727.6010301@tvcablenet.be \
--to=francois.valenduc@tvcablenet.be \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).