From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net,
Kenneth Lavrsen <kenneth@lavrsen.dk>,
Jesper Juhl <juhl-lkml@dif.dk>, Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Re: Summarizing the PWC driver questions/answers
Date: Sun, 29 Aug 2004 14:40:00 +0100 [thread overview]
Message-ID: <1093786799.27934.28.camel@localhost.localdomain> (raw)
In-Reply-To: <200408280113.27530.oliver@neukum.org>
On Sad, 2004-08-28 at 00:13, Oliver Neukum wrote:
> Keeping drivers against the wishes of the authors in the tree would
> be very troubling for the future. I can assure you that no maintainer
> will lightly pull a driver in this way.
Then the kernel community is no longer fit to use my code. So you should
remove everything I've written from Linus kernel too. I'll maintain my
own kernel.
Oh gosh, look I've just crippled Linus tree and stolen his project.
Thats *WHY* you can't just rip drivers out. A license was granted, for
ever. You can certainly remove him from maintainers, and if he insists
from the author credits.
Alan
next prev parent reply other threads:[~2004-08-29 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 19:54 Summarizing the PWC driver questions/answers Kenneth Lavrsen
2004-08-27 20:14 ` [linux-usb-devel] " David Brownell
2004-08-27 20:22 ` David S. Miller
2004-08-27 20:30 ` David Ford
2004-08-27 21:26 ` Wouter Van Hemel
2004-08-27 22:07 ` [OT] " David Ford
2004-08-27 20:32 ` Zwane Mwaikambo
2004-08-27 21:25 ` Jesper Juhl
[not found] ` <Pine.LNX.4.61.0408272259450.2771@dragon.hygekrogen.localho st>
2004-08-27 22:08 ` Kenneth Lavrsen
2004-08-27 23:01 ` Bernd Petrovitsch
2004-08-27 23:13 ` [linux-usb-devel] " Oliver Neukum
2004-08-29 13:40 ` Alan Cox [this message]
2004-08-30 9:14 ` Craig Milo Rogers
2004-08-31 5:04 ` asterix the gual
2004-08-28 0:22 ` Paul Jakma
2004-08-28 15:55 ` [linux-usb-devel] " michel Xhaard
2004-08-30 12:04 ` Geert Uytterhoeven
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=1093786799.27934.28.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=juhl-lkml@dif.dk \
--cc=kenneth@lavrsen.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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