From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Best way to send several patches
Date: Fri, 06 Aug 2010 00:06:19 +0200 [thread overview]
Message-ID: <4C5B35DB.7010302@s5r6.in-berlin.de> (raw)
In-Reply-To: <AANLkTin5gz-NBGYrmdOQ4F4s-fbETq642JVsHEEJY4HD@mail.gmail.com>
Bjarke Istrup Pedersen wrote:
> I'm reading on the kernelnewbies wiki about janitor work needing be to done.
> I have been cleaning up some stuff, and have alot of patches (I have
> split my changed into smaller patches).
Good.
> The question is, should I just send them all to this mailinglist
> (Section 3 of Documentation/SubmittingPatches - the one with the patch
> bomb - suggest that this is a bad idea), or how should I do it? (I
> have only submitted a single patch before, so I didn't have to worry
> about that back then).
>
> I have been thinking about sending a pull request, but since I've only
> done one patch up until now, I find it unlikely to be trusted enough
> to get a pull request through (correct me if I'm wrong).
Send the patches to the respective subsystem mailinglist. Cc the
responsible maintainer and lkml.
However, the current time is not ideal: A merge window is open, with
code in the mainline changing quickly and maintainers being busy with
integration; not helped by the fact that some Linux conferences are
imminent. Consider to wait until 2.6.36-rc1 was released, then check
whether your patches are still applicable on top of 2.6.36-rc1, then
post them.
--
Stefan Richter
-=====-==-=- =--- --=-=
http://arcgraph.de/sr/
prev parent reply other threads:[~2010-08-05 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:54 Bjarke Istrup Pedersen
2010-08-05 22:02 ` Roland Dreier
2010-08-05 22:25 ` Bjarke Istrup Pedersen
2010-08-05 22:06 ` Stefan Richter [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=4C5B35DB.7010302@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=gurligebis@gentoo.org \
--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®