From: Junio C Hamano <junkio@cox.net>
To: "Sean" <seanlkml@sympatico.ca>
Cc: "Adrian Bunk" <bunk@stusta.de>,
"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: Wed, 11 Jan 2006 18:22:43 -0800 [thread overview]
Message-ID: <7vu0cagp70.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <BAYC1-PASMTP11D76F1C8E40096264A62CAE240@CEZ.ICE> (seanlkml@sympatico.ca's message of "Tue, 10 Jan 2006 20:38:23 -0500 (EST)")
"Sean" <seanlkml@sympatico.ca> writes:
>> 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.
I agree with Adrian on this point. The
kernel-list patch reviewing process only depends on "diff -pu"
format, and git obviously gives its users an easy way to
generate such, but so would other tools.
The number of patches on the kernel list that are coming from
git does not really matter, but even if it did, they seem to be
a very small minority.
This is SubmittingPatches document that is being discussed, not
LinusPleasePull document. The latter would naturally _require_
the developer to use git, but not the former.
next prev parent reply other threads:[~2006-01-12 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 21:43 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
2006-01-12 2:22 ` Junio C Hamano [this message]
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=7vu0cagp70.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=imcdnzl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
--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
Powered by JetHome