From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Dan Williams" <dcbw@redhat.com>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870
Date: Wed, 14 Oct 2009 16:52:40 +0200 [thread overview]
Message-ID: <200910141652.41041.bzolnier@gmail.com> (raw)
In-Reply-To: <20091014140923.GA2890@tuxdriver.com>
On Wednesday 14 October 2009 16:09:24 John W. Linville wrote:
> On Tue, Oct 13, 2009 at 11:57:57PM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> > Several months later (after all current users are happy with the improved
> > drivers) the old drivers will be removed from staging..
>
> I _really_ hope this isn't the standard. By that measure, nothing
> will ever leave staging as _someone_ will always have some use case
> that makes the other driver better for them.
Doesn't seem to be the case with all other drivers except wireless ones
and the only real reason why wireless ones are so special is because of:
"But then there's the users, who bitch about everything and simply do
not understand what it is at stake.
And all this is becoming way too messy for us to handle.
Personally all I see around me is people bitching and complaining, and
no code being ported."
attitude which pretty much explains the problem..
Please adjust the process to fix the problem yourself or if you do not
want to do it just make the room for people who do.
next prev parent reply other threads:[~2009-10-14 14:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:24 Current status of rt2800usb and staging/rt2870 Ozan Çağlayan
2009-10-13 15:52 ` Ivo van Doorn
2009-10-13 17:27 ` Bartlomiej Zolnierkiewicz
2009-10-13 18:17 ` Ivo van Doorn
2009-10-13 19:21 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:00 ` Ivo van Doorn
2009-10-13 20:42 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:15 ` Dan Williams
2009-10-13 21:57 ` Bartlomiej Zolnierkiewicz
2009-10-13 22:21 ` Luis Correia
2009-10-14 14:14 ` John W. Linville
2009-10-13 22:24 ` Dan Williams
2009-10-13 22:42 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:15 ` John W. Linville
2009-10-14 13:51 ` Ivo van Doorn
2009-10-14 14:09 ` John W. Linville
2009-10-14 14:52 ` Bartlomiej Zolnierkiewicz [this message]
2009-10-14 14:56 ` John W. Linville
2009-10-14 15:28 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:47 ` John W. Linville
2009-10-14 17:33 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:26 ` Luis Correia
2009-10-14 20:41 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:56 ` Ivo van Doorn
2009-10-14 20:10 ` Bartlomiej Zolnierkiewicz
2009-10-15 6:28 ` Gertjan van Wingerde
2009-10-15 9:47 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:55 ` Luis R. Rodriguez
2009-10-15 14:47 ` Bartlomiej Zolnierkiewicz
2009-10-15 19:06 ` Luis R. Rodriguez
2009-10-16 17:13 ` Bartlomiej Zolnierkiewicz
2009-10-14 1:52 ` Mike Galbraith
2009-10-13 16:44 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:41 ` Ozan Çağlayan
2009-10-13 20:44 ` Bartlomiej Zolnierkiewicz
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=200910141652.41041.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=dcbw@redhat.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ozan@pardus.org.tr \
/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).