mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] [USB] UASP: USB Attached SCSI (UAS) protocol driver
Date: Mon, 13 Dec 2010 14:37:39 -0800	[thread overview]
Message-ID: <20101213223739.GD15472@one-eyed-alien.net> (raw)
In-Reply-To: <72920.27902.qm@web31804.mail.mud.yahoo.com>

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

On Mon, Dec 13, 2010 at 01:46:58PM -0800, Luben Tuikov wrote:
> --- On Sat, 12/11/10, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > 
> > > Alan, don't you work for the same company as do the
> > authors listed in "uas.c"?
> > 
> > If you've got nothing better to do than insinuate further
> > unpleasant
> > things when people try and help then don't expect any help
> > from anyone.
> > 
> > *plonk*
> 
> When in doubt, follow the money.

Luben, let me congratulate you.  You are the first person ever to be put
into my killfile.  Ever.  This is a first, and I have personal e-mail
archives stretching back almost 2 decades.  This will be my last message to
you; I would have to look to see if it was the only one.

Your insinuations against the character of many long-standing Linux
developers, based on their refusal to accept your submission, are simply
beyond the pale.  I could just as easily make every one of these
accusations against you -- who pays your salary, for example?  What are
their interests?  You make claims about your motivations, but how am I to
verify any of those?

The linux community works because it is exactly that -- a community.  We
have, just like any other community, standards of decorum.  You have
violated those standards, repeatedly, despite several people politely
telling you the proper manner in which to behave.

> Did you review my driver? Did anyone else in this thread? No, of course
> not. You didn't even do it the second time I called your bluff in this
> thread. Why not? Simple, it's not what you're getting paid to do now.

*bzzt*  Wrong.  I did review your driver.  I found it interesting, but upon
first submission I found no compelling reason to prefer it over the old.
Your initial submission gave no such reasons.

It was only until, after your submission was refused, that you addressed
the technical merits of your driver over the existing one.  I will admit,
you have some valid technical points.  But, they are completely overridden
by your inability to work within the standards of behavior of the community.

If, at any time, you had decided to stop using ad-hominem attacks and
instead made a calm, composed, and well-reasoned statement about why the
work to fixup the existing driver would be worse than doing a drop-in
replacement, we would have listened.  You came pretty close to doing this,
but seemed completely unable to resist personal attacks against members of
this community.  And you never really addressed, beyond a 1-line statement
stating that to fixup the existing driver you would need to replace it
wholesale, why working to improve the existing driver is a bad choice.

We look to submitters to maintain their work.  Yes, there are apparently
some difficulties getting Matt W. to push the ball forward on his UAS
driver.  However, dealing with you is comparable to drinking napalm; I
would much rather deal with someone who is less-than-responsive rather than
someone who is abrasive.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

We can customize our colonels.
					-- Tux
User Friendly, 12/1/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2010-12-13 22:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 21:46 Luben Tuikov
2010-12-13 22:37 ` Matthew Dharm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-14 17:25 Luben Tuikov
2010-12-14 18:12 ` Ben Gamari
2010-12-15 22:17   ` Luben Tuikov
2010-12-16  6:29   ` Andreas Mohr
2010-12-16  9:46     ` Luben Tuikov
2010-12-16 12:11       ` Andreas Mohr
2010-12-10 23:15 Luben Tuikov
2010-12-10 23:42 ` Alan Cox
2010-12-11  2:26   ` Luben Tuikov
2010-12-13 18:40     ` Mark Brown
2010-12-13 19:48       ` Matthias Schniedermeyer
2010-12-13 21:53         ` Luben Tuikov
2010-12-13 21:53         ` Andreas Mohr
2010-12-14  0:42           ` Sarah Sharp
2010-12-14  8:30             ` Luben Tuikov
2010-12-13 21:34       ` Luben Tuikov
2010-12-09  0:16 Luben Tuikov
2010-12-09  1:52 ` Greg KH
2010-12-09  2:26   ` Matthew Dharm
2010-12-06 17:05 Luben Tuikov
2010-12-06 17:09 ` Greg KH

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=20101213223739.GD15472@one-eyed-alien.net \
    --to=mdharm-kernel@one-eyed-alien.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    /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

all inboxes | Powered by JetHome®