From: Alejandro Bonilla <abonilla@linuxwireless.org>
To: linux-kernel@vger.kernel.org
Subject: Creating patches for source
Date: Thu, 26 May 2005 20:21:43 -0500 [thread overview]
Message-ID: <42967627.5040306@linuxwireless.org> (raw)
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?
Thanks for the time,
.Alejandro
next reply other threads:[~2005-05-27 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 1:21 Alejandro Bonilla [this message]
2005-05-27 2:34 ` Creating patches for source randy_dunlap
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=42967627.5040306@linuxwireless.org \
--to=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