linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lang <david.lang@digitalinsight.com>
To: linux-kernel@vger.kernel.org
Subject: Is this still the linux-kernel list?
Date: Tue, 12 Jun 2001 23:11:33 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0106122304440.26275-100000@dlang.diginsite.com> (raw)

I ask this (tounge in cheek) becouse some of the comments I have seen this
month seem so out of place.

first we had the 'this portion of the kernel is not subject to change by
anyone but me' post

now we have the 'code from this company or anyone working there is not
acceptable (now matter how well written) and may not even be looked at'

this sure doesn't seem like the same list that I have been reading for the
last four years.

remember guys, it's supposed to be about the code. As long as the code is
under an acceptable license who it's from or what it's going to touch
isn't supposed to be the issue, the issue is supposed to be 'is this code
an improvement (in performance, style, algorithm, etc combined)' if it is
it makes it in.

also I think it's fair to point out that maintainers who were perceived as
getting to possesive about their 'piece' of the kernel have been replaced
before, don't work your way into a corner and encourage someone to replace
you (for one thing the new guy makes mistakes as they are learning things
and it's painful for the rest of us :-)

David Lang


             reply	other threads:[~2001-06-13  7:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13  6:11 David Lang [this message]
     [not found] ` <20010613111640.C29895@pc8.lineo.fr>
2001-06-13 10:05   ` Is this still the linux-kernel list? christophe barbé

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=Pine.LNX.4.33.0106122304440.26275-100000@dlang.diginsite.com \
    --to=david.lang@digitalinsight.com \
    --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).