linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: over&out (Re: feature request - why not make netif_rx() a pointer?)
Date: Wed, 23 Oct 2002 15:59:16 -0700	[thread overview]
Message-ID: <20021023225916.GA6395@pegasys.ws> (raw)
In-Reply-To: <008b01c27ab0$760be900$800a140a@SLNW2K>

On Wed, Oct 23, 2002 at 12:23:03PM -0400, Slavcho Nikolov wrote:
> Chris Friesen wrote
> | I don't think you understand the nature of the GPL and linux development.
> 
> What a presumptuous opening statement!

It is a statement of opinion based on proximate evidence and
was phrased as such.  Only a statement of fact not in
evidence could have been presumptuous.  You could persuade
us that he is wrong by showing us your applicable
understanding.

> | The kernel developers do not have any obligation to anything other than
> | technical excellence.  You're getting a highly optimized operating
> | system *at no financial cost*.  In return, the community requires that
> | certain types of modifications be made publicly available.
> 
> Yes, many companies from time to time feed smaller or larger contributions
> back into the community.
> But they don't usually release *all* their modifications because they just
> might be irrelevant to everyone but a small niche of enterprise users.

That is obviously untrue or a complete misunderstanding.

Even the tiniest, most specialized patch is more relevant
than a spelling error in a comment or some crook from
Nigeria asking for access to our bank accounts.  If the
patches are really irrelevant then it won't matter to you if
they are publicly available.  Maybe they won't seem so
irrelevant to someone else.

There would be little objection to their posting these
irrelevant modifications here.  The GPL only requires that
they be made available.  Stick them somewhere on your web
site with an obscure link pointing to them.

Irrelevance is no reason not to share patches.  Shamefully
bad code i can see not sharing, but such bad code shouldn't
be in a commercial offering.  The only reason not to share
commercially viable patches is the same reason the Linux
kernel is GPL.

Pay the price (free code) or shop somewhere else.  With GPL
that is _your_ choice.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2002-10-23 22:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  0:39 feature request - why not make netif_rx() a pointer? Jean Tourrilhes
2002-10-23 13:39 ` Slavcho Nikolov
2002-10-23 14:03   ` Chris Friesen
2002-10-23 16:23     ` over&out (Re: feature request - why not make netif_rx() a pointer?) Slavcho Nikolov
2002-10-23 22:59       ` jw schultz [this message]
2002-10-24  6:25         ` Gilad Ben-Yossef
2002-10-24  7:08           ` Ben Greear
2002-10-25 11:50       ` Adrian Bunk
2002-10-23 16:48   ` feature request - why not make netif_rx() a pointer? Jean Tourrilhes
2002-10-23 17:27     ` Ben Greear
2002-10-24  4:13   ` David S. Miller
2002-10-24  9:28     ` Henning P. Schmiedehausen
2002-10-24 10:15       ` David S. Miller
2002-10-24 11:01         ` Henning Schmiedehausen
2002-10-24 13:30     ` Slavcho Nikolov
2002-10-24 13:46       ` David S. Miller

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=20021023225916.GA6395@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).