From: Ian McDonald <imcdnzl@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>, trivial@rustcorp.com.au
Subject: [PATCH] Documentation: Update to SubmittingPatches
Date: Tue, 20 Dec 2005 15:31:01 +1300 [thread overview]
Message-ID: <cbec11ac0512191831j563ea167vc5a63e11a34c7ef9@mail.gmail.com> (raw)
from ian McDonald
Use of git-diff
Signed-off-by: Ian McDonald <imcdnzl@gmail.com>
---
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 237d54c..b8d746a 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -20,10 +20,24 @@ SECTION 1 - CREATING AND SENDING YOUR CH
-1) "diff -up"
-------------
+1) Creating a diff file
+-----------------------
-Use "diff -up" or "diff -uprN" to create patches.
+You can use git-diff which makes your life easy. If you want it to be more
+difficult then carry on reading.
+
+Make sure your patch does not include any extra files which do not
+belong in a patch submission. Make sure to review your patch -after-
+generated it with diff(1), to ensure accuracy.
+
+If your changes produce a lot of deltas, you may want to look into
+splitting them into individual patches which modify things in
+logical stages. This will facilitate easier reviewing by other
+kernel developers, very important if you want your patch accepted.
+There are a number of scripts which can aid in this:
+
+Use "diff -up" or "diff -uprN" to create patches
+------------------------------------------------
All changes to the Linux kernel occur in the form of patches, as
generated by diff(1). When creating your patch, make sure to create it
@@ -61,16 +75,6 @@ patch. The "dontdiff" file is included
2.6.12 and later. For earlier kernel versions, you can get it
from <http://www.xenotime.net/linux/doc/dontdiff>.
-Make sure your patch does not include any extra files which do not
-belong in a patch submission. Make sure to review your patch -after-
-generated it with diff(1), to ensure accuracy.
-
-If your changes produce a lot of deltas, you may want to look into
-splitting them into individual patches which modify things in
-logical stages. This will facilitate easier reviewing by other
-kernel developers, very important if you want your patch accepted.
-There are a number of scripts which can aid in this:
-
Quilt:
http://savannah.nongnu.org/projects/quilt
next reply other threads:[~2005-12-20 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 2:31 Ian McDonald [this message]
2005-12-20 3:40 ` Junio C Hamano
2005-12-20 21:41 ` Ian McDonald
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=cbec11ac0512191831j563ea167vc5a63e11a34c7ef9@mail.gmail.com \
--to=imcdnzl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trivial@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®