mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>, Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH RFC] Docs: Modernize SubmittingPatches
Date: Thu, 18 Dec 2014 19:28:16 +0000	[thread overview]
Message-ID: <20141218192816.GC11764@sirena.org.uk> (raw)
In-Reply-To: <20141215105251.16913f8c@lwn.net>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

On Mon, Dec 15, 2014 at 10:52:51AM -0500, Jonathan Corbet wrote:

> +15) 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.
> +As a result, many subsystem maintainers are reluctant to take pull
> +requests, especially from new, unknown developers.

Probably worth adding something like "If in doubt you can use the pull
request as the cover letter for a normal posting of the patch series,
giving the maintainer the option of using either or both" - that way
even if someone guesses wrong about the pull request being appropriate
things will most likely be OK anyway.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      parent reply	other threads:[~2014-12-18 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 15:52 Jonathan Corbet
2014-12-15 16:33 ` Randy Dunlap
2014-12-15 21:58   ` Jonathan Corbet
2014-12-15 20:29 ` Frank Rowand
2014-12-15 22:42 ` Corey Minyard
2014-12-18 19:28 ` Mark Brown [this message]

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=20141218192816.GC11764@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=cminyard@mvista.com \
    --cc=corbet@lwn.net \
    --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

all inboxes | Powered by JetHome®