From: randy_dunlap <rdunlap@xenotime.net>
To: Alejandro Bonilla <abonilla@linuxwireless.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Creating patches for source
Date: Thu, 26 May 2005 19:34:37 -0700 [thread overview]
Message-ID: <20050526193437.2fd71090.rdunlap@xenotime.net> (raw)
In-Reply-To: <42967627.5040306@linuxwireless.org>
On Thu, 26 May 2005 20:21:43 -0500 Alejandro Bonilla wrote:
| Hi,
|
| Quick and fast question here. I'm starting to create patches (diff)
| :-) so, I googled for a while and most say that one could use the diff
| -up or diff -Naur. They both look to me very similar and honestly -up
| works for me. Still, what command will make the cleanest patch and which
| one is mostly used?
You looked at 'man diff', right?
and linux/Documentation/SubmittingPatches, which says:
Use "diff -up" or "diff -uprN" to create patches.
So you use the options that are appropriate for your patches.
If you are patching only one file (or a few files in the same
directory), -up is usually fine.
If you have patches in multiple directories and you want diff
to search in subdirectories for patches, you need to use -r
(recursive).
If you are adding new files, you need to use -N.
Is there a specific problem that you are trying to solve?
---
~Randy
next prev parent reply other threads:[~2005-05-27 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 1:21 Alejandro Bonilla
2005-05-27 2:34 ` randy_dunlap [this message]
2005-05-27 1:48 ` Alejandro Bonilla
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=20050526193437.2fd71090.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=abonilla@linuxwireless.org \
--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
all inboxes | Powered by JetHome®