From: David Miller <davem@davemloft.net>
To: elendil@planet.nl
Cc: netdev@vger.kernel.org
Subject: Re: When best to submit patches with small changes in multiple files?
Date: Wed, 10 Mar 2010 07:34:48 -0800 (PST) [thread overview]
Message-ID: <20100310.073448.27419654.davem@davemloft.net> (raw)
In-Reply-To: <201003100449.12952.elendil@planet.nl>
From: Frans Pop <elendil@planet.nl>
Date: Wed, 10 Mar 2010 04:49:12 +0100
> I have patches prepared to remove trailing spaces from kernel messages
> for ./net and ./drivers/net (including wireless).
>
> In total 15 patches with
> 81 files changed, 351 insertions(+), 351 deletions(-)
>
> When would be the best time to submit:
> - now, to be included in .34
> - now, for -next
> - any time
> - near beginning of merge window (rebased against netdev-next)
> - not at all ;-)
Later, for -next. Submit them say in a week or two.
next prev parent reply other threads:[~2010-03-10 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 3:49 When best to submit patches with small changes in multiple files? Frans Pop
2010-03-10 15:34 ` David Miller [this message]
2010-03-10 16:52 ` Frans Pop
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=20100310.073448.27419654.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=elendil@planet.nl \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).