mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Paul Jackson <pj@sgi.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
	gregkh@suse.de, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC] HOWTO do Linux kernel development
Date: Mon, 14 Nov 2005 17:31:18 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0511141729360.20249@shark.he.net> (raw)
In-Reply-To: <20051114172544.31c87778.pj@sgi.com>

On Mon, 14 Nov 2005, Paul Jackson wrote:

> Josh wrote:
> > In a community that is looking for the best technical solution
> > possible, there is no place for ego.
>
> No, there is a place for ego, an essential place.  Some of the best
> hackers on lkml have no shortage of ego.  They just don't get their ego
> too closely attached to any particular piece of code or technical
> position.  Rather they take pride in their willingness and ability to
> find better answers (even in their own work, done five minutes ago ;).
>
> I don't normally quote Colin Powell (a recent U.S. Secretary of State),
> but this one time he said it well:
>
>
> 	Avoid having your ego so close to your position that
> 	when your position falls, your ego goes with it.
>
> 					-- Colin Powell

Nice advice.  I (too often) see people who are working on the
<technology du jour> to be so tied up with it that they
think it's the greatest thing around.

> Ego deficient pansies risk wilting on lkml.

-- 
~Randy

  reply	other threads:[~2005-11-15  1:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:07 Greg KH
2005-11-14 22:10 ` Greg KH
2005-11-14 22:43   ` [RFC] [HUMOR] " Jeffrey V. Merkey
2005-11-15  0:18   ` [RFC] " Kalin KOZHUHAROV
2005-11-15  0:32     ` Randy.Dunlap
2005-11-15  4:58     ` Greg KH
2005-11-15  8:37       ` Paolo Ciarrocchi
2005-11-15 19:04         ` Greg KH
2005-11-15  0:32   ` Josh Boyer
2005-11-15  1:25     ` Paul Jackson
2005-11-15  1:31       ` Randy.Dunlap [this message]
2005-11-15  2:16       ` Josh Boyer
2005-11-15  2:42         ` Paul Jackson
2005-11-15  2:52           ` Josh Boyer
2005-11-15  3:01             ` Paul Jackson
2005-11-15  4:48               ` Greg KH
2005-11-15  4:47             ` Greg KH
2005-11-15  1:08 ` Coywolf Qi Hunt
2005-11-15  4:38   ` Greg KH
2005-11-15  5:51     ` Coywolf Qi Hunt
2005-11-15  5:52       ` Greg KH
2005-11-15  6:31         ` Coywolf Qi Hunt
2005-11-17 13:54         ` Pavel Machek
2005-11-15 14:42 ` Andi Kleen
2005-11-15 17:33   ` Greg KH
2005-11-16  8:12     ` Michael Kerrisk
2005-11-17  6:56       ` Greg KH
2005-11-17 12:12         ` Michael Kerrisk
2005-11-15 20:10 ` Luca
2005-11-15 20:13   ` Josh Boyer
2005-11-15 20:56   ` Greg KH
2005-11-16  4:38     ` Randy.Dunlap
2005-11-15 22:20   ` sitexec
2005-11-16 12:15 linux

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.58.0511141729360.20249@shark.he.net \
    --to=rdunlap@xenotime.net \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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

Powered by JetHome