From: David Miller <davem@davemloft.net>
To: isdn@linux-pingi.de
Cc: netdev@vger.kernel.org, isdn4linux@listserv.isdn4linux.de
Subject: Re: [PATCH 00/28] MISDN patchset for net-next
Date: Mon, 23 Apr 2012 15:19:53 -0400 (EDT) [thread overview]
Message-ID: <20120423.151953.1258613141357490104.davem@davemloft.net> (raw)
In-Reply-To: <20120423170549.33CDA9FB80@pingi6.linux-pingi.de>
From: Karsten Keil <isdn@linux-pingi.de>
Date: Mon, 23 Apr 2012 18:03:51 +0200
> please include thes patches into netnext.
Please submit smaller, reasonable, amounts of patches at one time.
Say 10 or so.
Coming out of the blue with a 28 entry patch bomb is not acceptable.
Also, please do not let whatever you're using to submit these patches
take the email date from the commit timestamp in your local tree.
This makes no sense when your submitting patches for someone to apply,
and utterly screws up the order in which the patches show up in
patchwork:
http://patchwork.ozlabs.org/project/netdev/list/
prev parent reply other threads:[~2012-04-23 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 16:03 [PATCH 00/28] MISDN patchset for net-next Karsten Keil
2012-04-23 19:19 ` David Miller [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=20120423.151953.1258613141357490104.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--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).