public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: Kenneth Lavrsen <kenneth@lavrsen.dk>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Albert Cahalan <albert@users.sourceforge.net>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	pmarques@grupopie.com, greg@kroah.com, nemosoft@smcc.demon.nl,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: pwc+pwcx is not illegal
Date: Fri, 27 Aug 2004 16:38:08 -0400	[thread overview]
Message-ID: <412F9BB0.1010507@blue-labs.org> (raw)
In-Reply-To: <6.1.2.0.2.20040827215143.01d7b038@inet.uni2.dk>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]


Kenneth Lavrsen wrote:

> [...]
> Just look at the reaction everywhere. I have rarely seen so many angry 
> Linux users. I have already started contacting computer magazines and 
> news papers. I just cannot accept that people can care so little for 
> other people.
>
> Kenneth


One incredibly burning question sits before me.  Why do you spend such 
an exorbitant amount of energy wailing and hand waving over this instead 
of coming up with a solution?  You're so hellbent on making a big stink 
out of it instead of what seems to be a simple issue.  Since the driver 
already exists in multiple parts, use the existing works to come up with 
a solution.  I know Nemosoft loves his work and nobody likes getting 
pushed away.  But if the approach is wrong, find a solution that is right.

Honestly, it's pretty annoying to see people hellbent on the ruckus 
itself with little or no thought to a solution.

Make sure that gets into the editorials too.

-david


[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]

begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard


  parent reply	other threads:[~2004-08-27 20:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 19:18 pwc+pwcx is not illegal Albert Cahalan
2004-08-27 19:29 ` Linus Torvalds
2004-08-27 20:06   ` Kenneth Lavrsen
2004-08-27 20:21     ` Linus Torvalds
2004-08-27 20:24     ` David S. Miller
2004-08-27 20:26     ` Paul Jakma
2004-08-30 17:41       ` Brian Litzinger
2004-08-27 20:38     ` David Ford [this message]
2004-08-27 20:57   ` Albert Cahalan
2004-08-27 21:04     ` Greg KH
2004-08-27 21:09     ` Linus Torvalds
2004-08-29 14:00   ` Alan Cox
2004-08-29 16:33     ` Nemosoft Unv.
2004-08-29 15:42       ` Alan Cox
2004-08-29 17:17         ` [linux-usb-devel] " Randy.Dunlap
2004-08-29 17:16       ` Norbert van Nobelen
2004-08-27 19:34 ` Paulo Marques
2004-08-27 21:34   ` Albert Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28  8:15 Gabucino
2004-08-28 10:30 ` Vojtech Pavlik
2004-08-28 12:18 Kenneth Lavrsen
2004-08-28 13:11 ` Adrian Bunk
2004-08-28 15:24   ` Kenneth Lavrsen
2004-08-29 14:02   ` Alan Cox
2004-09-01 22:51     ` Rogier Wolff

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=412F9BB0.1010507@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=albert@users.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=kenneth@lavrsen.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=nemosoft@smcc.demon.nl \
    --cc=pmarques@grupopie.com \
    --cc=torvalds@osdl.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