From: John Kacur <jkacur@rogers.com>
To: Jim Nelson <james4765@cwazy.co.uk>
Cc: linux-kernel@vger.kernel.org, rddunlap@osdl.org
Subject: [PATCH][Documentation update]Re: diff command line?
Date: Tue, 08 Mar 2005 23:23:19 -0500 [thread overview]
Message-ID: <1110342199.5533.24.camel@linux.site> (raw)
In-Reply-To: <4229E219.20100@cwazy.co.uk>
On Sat, 2005-03-05 at 11:45, Jim Nelson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Russell King wrote:
> | On Sat, Mar 05, 2005 at 10:48:00AM -0500, Gene Heskett wrote:
> |
> |>What are the options normally used to generate a diff for public
> |>consumption on this list?
> |
> |
> | diff -urpN orig new
> |
> | where "orig" and "new" both contain the top level "linux" directory,
> | so the resulting patch can be applied with patch -p1.
> |
>
> You'd also want to add "-x dontdiff", using
>
> http://developer.osdl.org/rddunlap/scripts/dontdiff-osdl
>
> That way, you can do a diff, even if you have run a compile in one of the
> directory trees.
Hey, why isn't that is the documentation? I didn't hear of it until now.
Is this what most developers are using for 2.6, if so then we need the
following trivial documentation update. Created against the Docs in
2.6.11
--- SubmittingPatches.orig 2005-03-08 23:09:19.496223848 -0500
+++ SubmittingPatches 2005-03-08 23:18:52.192160832 -0500
@@ -60,6 +60,9 @@
the build process, and should be ignored in any diff(1)-generated
patch. dontdiff is maintained by Tigran Aivazian <tigran@veritas.com>
+For 2.6 kernels you can fetch dontdiff-osdl maintained by Randy Dunlap.
+wget http://developer.osdl.org/rddunlap/scripts/dontdiff-osdl
+
next prev parent reply other threads:[~2005-03-09 4:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 15:48 diff command line? Gene Heskett
2005-03-05 16:18 ` Russell King
2005-03-05 16:44 ` Gene Heskett
2005-03-05 16:45 ` Jim Nelson
2005-03-05 17:06 ` Gene Heskett
2005-03-09 4:23 ` John Kacur [this message]
2005-03-07 10:51 ` Michelle Konzack
2005-03-07 14:13 ` Catalin Marinas
2005-03-07 15:08 ` Michelle Konzack
2005-03-05 17:00 ` Kyle McMartin
2005-03-05 17:26 ` Alexey Dobriyan
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=1110342199.5533.24.camel@linux.site \
--to=jkacur@rogers.com \
--cc=james4765@cwazy.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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