All of lore.kernel.org
 help / color / mirror / Atom feed
From: jmerkey <jmerkey@utah-nac.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Greg Folkert <greg@gregfolkert.net>,
	Stuart MacDonald <stuartm@connecttech.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Greg's Decree! (was Re: Linus' decrees?)
Date: Fri, 25 Feb 2005 16:56:46 -0700	[thread overview]
Message-ID: <421FBB3E.3040509@utah-nac.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10502242305190.23632-100000@master.linux-ide.org>


His point and direction (or lack thereof) are easy to see, and 
consistent. Linux has been a war of attrition
with an interesting rat's maze model of human intereaction -- always 
interesting to see new mice traverse the
maze (only there's no cheese at the end of this maze -- just the smell 
of cheese -- the cheese is on Linus'
desk outside the maze, and all the mice inside the maze are madly 
looking for it, and being driven
quite mad). :-)

Cheers,

Jeff

Andre Hedrick wrote:

>Greg,
>
>Linus is not always correct, sometimes his point of view is hard to see.
>My shoulders got in the way most of the time; however, Linus is
>consistant.  Well until he changes his mind.
>
>Crack ??  Get some plumber's putty to smooth over the gap.
>
>Cheers,
>
>Andre Hedrick
>LAD Storage Consulting Group
>
>On Thu, 24 Feb 2005, Greg Folkert wrote:
>
>  
>
>>On Thu, 2005-02-24 at 15:03 -0500, Stuart MacDonald wrote:
>>    
>>
>>>Recently I ran across
>>>http://groups.google.ca/groups?hl=en&lr=lang_en&safe=off&selm=1033074519.2698.5.
>>>camel%40localhost.localdomain
>>>
>>>Is there a collection point for Linus' decrees?
>>>
>>>The LSB (http://www.linuxbase.org/) seems to be mostly involved with
>>>how a distro is laid out, and not much to do with the kernel.
>>>      
>>>
>>Okay, Linus decreed... oh yeah.
>>
>>Exactly what is wrong with the method anyway?
>>
>>You on Crack?
>>
>>And no... that is not a decree in the traditional sense. It is more like
>>me saying:
>>        "I decree that Linus Torvalds is the lead maintainer of the
>>        Linux Kernel"
>>
>>Make TONS-O-SENSE to state the obvious. IOW the statement was all meant
>>to say *DO IT THIS WAY AND NO OTHER* as nobody else honors any other
>>method.
>>-- 
>>greg, greg@gregfolkert.net
>>
>>The technology that is
>>Stronger, better, faster: Linux
>>
>>    
>>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>


  reply	other threads:[~2005-02-25 23:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 20:03 Linus' decrees? Stuart MacDonald
2005-02-24 21:30 ` Greg's Decree! (was Re: Linus' decrees?) Greg Folkert
2005-02-24 22:08   ` Stuart MacDonald
2005-02-24 22:40     ` Randy.Dunlap
2005-02-25  0:55       ` Horst von Brand
2005-02-25 14:45         ` Stuart MacDonald
2005-02-25  6:56     ` Valdis.Kletnieks
2005-02-25 14:51       ` Greg's Policy! (was Re: Linus' policies?) Stuart MacDonald
2005-02-25 13:48     ` Greg's Decree! (was Re: Linus' decrees?) Theodore Ts'o
2005-02-25  7:07   ` Andre Hedrick
2005-02-25 23:56     ` jmerkey [this message]
2005-02-25  7:04 ` Linus' decrees? Andre Hedrick

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=421FBB3E.3040509@utah-nac.org \
    --to=jmerkey@utah-nac.org \
    --cc=andre@linux-ide.org \
    --cc=greg@gregfolkert.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuartm@connecttech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.