From: Adrian Bunk <bunk@stusta.de>
To: Ian McDonald <imcdnzl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
trivial@kernel.org, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Revised [PATCH] Documentation: Update to SubmittingPatches
Date: Wed, 11 Jan 2006 01:57:21 +0100 [thread overview]
Message-ID: <20060111005721.GA29663@stusta.de> (raw)
In-Reply-To: <cbec11ac0512201343q79de6e13h6fccf1259445076@mail.gmail.com>
On Wed, Dec 21, 2005 at 10:43:40AM +1300, Ian McDonald wrote:
> Updated documentation for submitting patches taking account of git.
>
> Signed-off-by: Ian McDonald <imcdnzl@gmail.com>
> ---
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 237d54c..8756475 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(1) or git-format-patch(1) which makes your life easy. If
> +you want it to be more difficult then carry on reading.
>...
IMHO, this doesn't make much sense:
The average patch submitter does _not_ use git in any way - and there's
no reason why he should.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-11 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 21:43 Revised [PATCH] Documentation: Update to SubmittingPatches Ian McDonald
2006-01-11 0:57 ` Adrian Bunk [this message]
[not found] ` <46118.10.10.10.28.1136943503.squirrel@linux1>
2006-01-11 1:38 ` Sean
2006-01-12 2:22 ` Junio C Hamano
2006-01-11 1:54 ` Adrian Bunk
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=20060111005721.GA29663@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=imcdnzl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trivial@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