public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [HUMOR] HOWTO do Linux kernel development
Date: Mon, 14 Nov 2005 15:43:41 -0700	[thread overview]
Message-ID: <4379131D.40007@wolfmountaingroup.com> (raw)
In-Reply-To: <20051114221005.GA5539@kroah.com>

Greg KH wrote:

>On Mon, Nov 14, 2005 at 02:07:09PM -0800, Greg KH wrote:
>  
>
>>So, I've been working on a document for the past week or so to help
>>alleviate a lot of these problems.
>>    
>>
>
>Oh, the latest version can be found at:
>	http://www.kernel.org/git/?p=linux/kernel/git/gregkh/patches.git;a=blob;f=HOWTO
>as I'm keeping it in my git patch tree.
>
>thanks,
>
>greg k-h
>-
>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/
>
>  
>
I'd like to add some sections to the doc.

APPENDIX E.

Chapter 1. How to get rich on IPO's and how to get people to give you IP 
for free and work like slaves simply for attribution.
Chapter 2. How to setup a kernel development rat maze with no cheese in 
the maze (only the smell of cheese).
Chapter 3. Rat Races. How to get the rats to run the maze and keep the 
maze clean.

NOTE: This email is a parody (joke) and should not be taken seriously.

:-)

Jeff





  reply	other threads:[~2005-11-15  0:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:07 [RFC] HOWTO do Linux kernel development Greg KH
2005-11-14 22:10 ` Greg KH
2005-11-14 22:43   ` Jeffrey V. Merkey [this message]
2005-11-15  0:18   ` 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
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

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=4379131D.40007@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=gregkh@suse.de \
    --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