public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: miller@techsource.com, jgarzik@pobox.com, dwmw2@infradead.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org, jeremy@sgi.com
Subject: Re: [DOC] Linux kernel patch submission format
Date: Thu, 23 Sep 2004 00:46:46 -0700	[thread overview]
Message-ID: <20040923004646.33c372f7.pj@sgi.com> (raw)
In-Reply-To: <200409221947.i8MJlnSX003715@laptop11.inf.utfsm.cl>

> diff(1) does what you want...

Not all he wanted.  There's more to a patch than the diff.

The following three documents explain how to submit patches to the
Linux kernel:

 1) Documentation/SubmittingPatches, a file in the kernel source
 2) Andrew Morton's "The Perfect Patch", available at:
      http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
 3) Jeff Garzik's "Linux kernel patch submission format", at:
      http://linux.yyz.us/patch-format.html

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

  reply	other threads:[~2004-09-23  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  8:08 [DOC] Linux kernel patch submission format Jeff Garzik
2004-08-31 11:41 ` Neil Horman
2004-08-31 16:17 ` Erik Mouw
2004-08-31 16:37 ` David Woodhouse
2004-08-31 17:15   ` Jeff Garzik
2004-08-31 17:17     ` David Woodhouse
2004-08-31 17:25       ` Jeff Garzik
2004-09-01  1:27       ` Lee Revell
2004-09-22 18:59     ` Timothy Miller
2004-09-22 19:47       ` Horst von Brand
2004-09-23  7:46         ` Paul Jackson [this message]
2004-09-24 15:04         ` Timothy Miller
2004-09-24 15:22           ` Randy.Dunlap
2004-10-20 19:34             ` Timothy Miller
2004-08-31 17:07 ` Sam Ravnborg
2004-08-31 17:11   ` Jeff Garzik
2004-08-31 17:50 ` Patrick Dreker
2004-08-31 18:01   ` Jeff Garzik

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=20040923004646.33c372f7.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=jeremy@sgi.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.com \
    --cc=vonbrand@inf.utfsm.cl \
    /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