From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: David.Choi@Micrel.Com, netdev@vger.kernel.org,
Ping.Doong@Micrel.Com, bhutchings@solarflare.com
Subject: Re: [PATCH net-next] drivers/net/ethernet/micrel/ks8851_mll: Implement basic statistics
Date: Tue, 29 Jan 2013 11:09:18 -0800 [thread overview]
Message-ID: <1359486558.15135.29.camel@joe-AO722> (raw)
In-Reply-To: <20130129.135523.2248566447781665296.davem@davemloft.net>
On Tue, 2013-01-29 at 13:55 -0500, David Miller wrote:
> Do not post new versions of patches as replies to other emails or
> threads, always use fresh, new list postings to post a patch.
I think replying with In-Reply-To: context is better
than starting a new thread without that In-Reply-To.
If the subject changes with version number, what
difference does it make?
Is there some case that patchwork doesn't handle well?
next prev parent reply other threads:[~2013-01-29 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:24 [PATCH net-next] drivers/net/ethernet/micrel/ks8851_mll: Implement basic statistics Choi, David
2013-01-29 18:42 ` Joe Perches
2013-01-29 18:55 ` David Miller
2013-01-29 19:09 ` Joe Perches [this message]
2013-01-29 19:18 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 18:46 Choi, David
2013-01-23 19:09 ` Joe Perches
2013-01-23 19:36 ` Choi, David
2013-01-29 1:34 ` Joe Perches
2013-01-28 23:39 ` David Miller
2013-01-29 1:21 ` Choi, David
2013-01-23 1:40 Choi, David
2013-01-23 1:51 ` David Miller
2013-01-23 3:57 ` Joe Perches
2013-01-23 4:17 ` David Miller
2013-01-23 4:27 ` Joe Perches
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=1359486558.15135.29.camel@joe-AO722 \
--to=joe@perches.com \
--cc=David.Choi@Micrel.Com \
--cc=Ping.Doong@Micrel.Com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--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).