From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Renzmann <mrenzmann@madwifi-project.org>,
madwifi-project@lists.madwifi-project.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [madwifi-project] [RFC] Closing the project
Date: Thu, 13 Nov 2008 16:11:58 -0500 [thread overview]
Message-ID: <1226610718.2904.23.camel@dv> (raw)
In-Reply-To: <43e72e890811131254q35ff4f48xf58c7c26d5c9a5a4@mail.gmail.com>
On Thu, 2008-11-13 at 12:54 -0800, Luis R. Rodriguez wrote:
> On Thu, Nov 13, 2008 at 12:48 PM, Pavel Roskin <proski@gnu.org> wrote:
> > It would be great to have a detailed analysis why MadWifi failed.
>
> It didn't fail, it was just not the best approach to support Linux
> from the start, that's why *today* its just silly to go on with it,
> specially since the vendor involved is *contributing* and helping to
> implement support the right way.
OK, I mean MadWifi failed to deliver what it could have delivered. It
failed to improve the code significantly. It failed to deal with the
bugs that could have been fixed. It failed to release the code that was
written by the team members. It failed to stabilize.
> >> Just my advice: let MadWifi die already, stop wasting your time.
> >
> > I understand what you mean, but I have to deal with MadWifi anyway. As
> > I said before, I'd rather share my fixes that keep them to myself.
>
> Understood -- but perhaps you can identify what is lacking that you
> need to better help push what is required and missing.
Specifically for me - just three letters. DFS.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Renzmann <mrenzmann@madwifi-project.org>,
madwifi-project@venema.h4ckr.net,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [madwifi-project] [RFC] Closing the project
Date: Thu, 13 Nov 2008 16:11:58 -0500 [thread overview]
Message-ID: <1226610718.2904.23.camel@dv> (raw)
In-Reply-To: <43e72e890811131254q35ff4f48xf58c7c26d5c9a5a4@mail.gmail.com>
On Thu, 2008-11-13 at 12:54 -0800, Luis R. Rodriguez wrote:
> On Thu, Nov 13, 2008 at 12:48 PM, Pavel Roskin <proski@gnu.org> wrote:
> > It would be great to have a detailed analysis why MadWifi failed.
>
> It didn't fail, it was just not the best approach to support Linux
> from the start, that's why *today* its just silly to go on with it,
> specially since the vendor involved is *contributing* and helping to
> implement support the right way.
OK, I mean MadWifi failed to deliver what it could have delivered. It
failed to improve the code significantly. It failed to deal with the
bugs that could have been fixed. It failed to release the code that was
written by the team members. It failed to stabilize.
> >> Just my advice: let MadWifi die already, stop wasting your time.
> >
> > I understand what you mean, but I have to deal with MadWifi anyway. As
> > I said before, I'd rather share my fixes that keep them to myself.
>
> Understood -- but perhaps you can identify what is lacking that you
> need to better help push what is required and missing.
Specifically for me - just three letters. DFS.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-11-13 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2576.194.45.26.221.1226491274.squirrel@webmail.madwifi.org>
[not found] ` <1226511194.9952.38.camel@dv>
[not found] ` <43e72e890811121224w4fc53e1s29080a42111186e9@mail.gmail.com>
[not found] ` <1226547092.11785.49.camel@dv>
2008-11-13 19:42 ` [madwifi-project] [RFC] Closing the project Luis R. Rodriguez
2008-11-13 19:42 ` Luis R. Rodriguez
2008-11-13 20:21 ` Stephen Clark
2008-11-13 20:38 ` Luis R. Rodriguez
2008-11-13 20:48 ` Pavel Roskin
2008-11-13 20:48 ` Pavel Roskin
2008-11-13 20:54 ` Luis R. Rodriguez
2008-11-13 20:54 ` Luis R. Rodriguez
2008-11-13 21:11 ` Pavel Roskin [this message]
2008-11-13 21:11 ` Pavel Roskin
2008-11-13 23:26 ` Derek Smithies
2008-11-13 23:26 ` Derek Smithies
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=1226610718.2904.23.camel@dv \
--to=proski@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=madwifi-project@lists.madwifi-project.org \
--cc=mcgrof@gmail.com \
--cc=mrenzmann@madwifi-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.