From: Roland Dreier <rdreier@cisco.com>
To: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Best way to send several patches
Date: Thu, 05 Aug 2010 15:02:05 -0700 [thread overview]
Message-ID: <adabp9g3ehu.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <AANLkTin5gz-NBGYrmdOQ4F4s-fbETq642JVsHEEJY4HD@mail.gmail.com> (Bjarke Istrup Pedersen's message of "Thu, 5 Aug 2010 23:54:09 +0200")
> 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 would suggest sending a small batch of patches (say, four or five at
most) and see how that goes. That way, in case you make some mistake in
formatting or something, you don't have to send another huge pile when
you resend.
Once your initial batch is accepted and you have the hang of submitting
patches, then you can submit bigger batches. But I would recommend
having each batch have a common theme. For example there was the recent
series of 42 fixes for confusing if indentation -- a big batch of fixes
for the same problem in different places, which is exactly the right way
to do things.
- Roland
--
Roland Dreier <rolandd@cisco.com> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
next prev parent reply other threads:[~2010-08-05 22:02 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 [this message]
2010-08-05 22:25 ` Bjarke Istrup Pedersen
2010-08-05 22:06 ` Stefan Richter
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=adabp9g3ehu.fsf@roland-alpha.cisco.com \
--to=rdreier@cisco.com \
--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®