From: David Miller <davem@davemloft.net>
To: william.allen.simpson@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH 4/4] TCPCT part 1: initial SYN exchange with SYNACK data
Date: Wed, 14 Oct 2009 23:17:10 -0700 (PDT) [thread overview]
Message-ID: <20091014.231710.63386795.davem@davemloft.net> (raw)
In-Reply-To: <4AD6B4F0.8060709@gmail.com>
When posting a patch series like this, use different subject
lines in each patch.
The subject line becomes the commit message header, and if
they are all the same nobody can figure out the general
idea of each part of the patch series when scanning the
commit header lines.
next prev parent reply other threads:[~2009-10-15 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 5:28 [net-next-2.6 PATCH 1/4] TCPCT part 1: initial SYN exchange with SYNACK data William Allen Simpson
2009-10-15 5:32 ` [net-next-2.6 PATCH 2/4] " William Allen Simpson
2009-10-15 5:34 ` [net-next-2.6 PATCH 3/4] " William Allen Simpson
2009-10-15 5:36 ` [net-next-2.6 PATCH 4/4] " William Allen Simpson
2009-10-15 6:17 ` David Miller [this message]
2009-10-15 6:15 ` [net-next-2.6 PATCH 1/4] " David Miller
2009-10-15 11:45 ` William Allen Simpson
2009-10-15 16:29 ` William Allen Simpson
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=20091014.231710.63386795.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=william.allen.simpson@gmail.com \
/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).