All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: netdev@vger.kernel.org
Subject: When best to submit patches with small changes in multiple files?
Date: Wed, 10 Mar 2010 04:49:12 +0100	[thread overview]
Message-ID: <201003100449.12952.elendil@planet.nl> (raw)

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 ;-)
?

Cheers,
FJP

             reply	other threads:[~2010-03-10  3:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  3:49 Frans Pop [this message]
2010-03-10 15:34 ` When best to submit patches with small changes in multiple files? David Miller
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=201003100449.12952.elendil@planet.nl \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.