From: Jonathan Corbet <corbet@lwn.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH 2/7] Docs: Bring SubmittingPatches more into the git era
Date: Wed, 9 Mar 2016 07:04:45 -0700 [thread overview]
Message-ID: <20160309070445.37d301cd@lwn.net> (raw)
In-Reply-To: <1457516710.118898.188.camel@infradead.org>
On Wed, 09 Mar 2016 09:45:10 +0000
David Woodhouse <dwmw2@infradead.org> wrote:
> On Tue, 2014-12-23 at 09:32 -0700, Jonathan Corbet wrote:
> >
> > -16) Sending "git pull" requests (from Linus emails)
> > +16) Sending "git pull" requests
> > +-------------------------------
> > +
> > +If you have a series of patches, it may be most convenient to have the
> > +maintainer pull them directly into the subsystem repository with a
> > +"git pull" operation. Note, however, that pulling patches from a developer
> > +requires a higher degree of trust than taking patches from a mailing list.
>
> This isn't really true, is it?
>
> If I accept a stream of patches in email, or if I accept them in a pull
> request, I can — and should — still actually *look* at what's being
> applied before I push it back out again.
I think I put something in there somewhere about a one-year statute of
limitation on review comments :)
I wrote that text that way because certain high-profile maintainers have
said exactly that sort of thing:
You can send me patches, but for me to pull a git patch from you,
I need to know that you know what you're doing, and I need to be
able to trust things *without* then having to go and check every
individual change by hand.
-- Mr. T. https://lwn.net/Articles/224135/
...and because, in truth, few maintainers do take pull requests. There
*is* some value in having the code out on the lists in the clear, it
raises the chances of somebody *else* looking it over slightly. There is
a reason why review is done on the lists, not directly from repositories.
Allowing the maintainer to attach tags certainly seems like another valid
reason to defer setting patches into git-implemented stone. But I don't
see it as the only one.
We could, I suppose, run a poll to ask maintainers why they are reluctant
to take pull requests. But the end result is kind of the same as far as
readers of SubmittingPatches are concerned - they need to send their
patches via email.
jon
next prev parent reply other threads:[~2016-03-09 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 16:32 [PATCH v2] Docs: Modernize SubmittingPatches Jonathan Corbet
2014-12-23 16:32 ` [PATCH 1/7] Docs: Remove "tips and tricks" from SubmittingPatches Jonathan Corbet
2014-12-23 16:32 ` [PATCH 2/7] Docs: Bring SubmittingPatches more into the git era Jonathan Corbet
2016-03-09 9:45 ` David Woodhouse
2016-03-09 11:44 ` Laszlo Ersek
2016-03-09 14:13 ` Jonathan Corbet
2016-03-09 14:04 ` Jonathan Corbet [this message]
2016-03-09 14:27 ` David Woodhouse
2014-12-23 16:32 ` [PATCH 3/7] Docs: Update recipient information in SubmittingPatches Jonathan Corbet
2014-12-23 16:32 ` [PATCH 4/7] Docs: SubmittingPatches: update follow-through instructions Jonathan Corbet
2014-12-23 16:32 ` [PATCH 5/7] Docs: SubmittingPatches: miscellaneous cleanups Jonathan Corbet
2014-12-23 16:32 ` [PATCH 6/7] Docs: Mention device tree binding info Jonathan Corbet
2014-12-23 16:32 ` [PATCH 7/7] Docs: SubmittingPatches: mention using pull requests as a cover letter Jonathan Corbet
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=20160309070445.37d301cd@lwn.net \
--to=corbet@lwn.net \
--cc=dwmw2@infradead.org \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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