linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sean" <seanlkml@sympatico.ca>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: "Ian McDonald" <imcdnzl@gmail.com>,
	"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: Tue, 10 Jan 2006 20:38:23 -0500 (EST)	[thread overview]
Message-ID: <BAYC1-PASMTP11D76F1C8E40096264A62CAE240@CEZ.ICE> (raw)
Message-ID: <46118.10.10.10.28.1136943503.squirrel@linux1> (raw)
In-Reply-To: <20060111005721.GA29663@stusta.de>

On Tue, January 10, 2006 7:57 pm, Adrian Bunk said:

>> -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.
>

Git is an efficient and convenient way to track the mainline kernel.   The
number of submitters using it is significant enough to mention it as an
option for creating patches.

Sean


  reply	other threads:[~2006-01-11  1:38 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
     [not found]   ` <46118.10.10.10.28.1136943503.squirrel@linux1>
2006-01-11  1:38     ` Sean [this message]
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=BAYC1-PASMTP11D76F1C8E40096264A62CAE240@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --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;
as well as URLs for NNTP newsgroup(s).