From: Pablo Neira Ayuso <pablo@netfilter.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linville@tuxdriver.com,
netfilter-devel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [README] Two merges pending...
Date: Wed, 23 May 2012 12:45:47 +0200 [thread overview]
Message-ID: <20120523104547.GA3312@1984> (raw)
In-Reply-To: <20120522.152840.815291543305899477.davem@davemloft.net>
Hi David,
On Tue, May 22, 2012 at 03:28:40PM -0400, David Miller wrote:
[...]
> Pablo also has a prearranged netfilter merge pending.
I give up on that merge that I requested.
I thought that some namespace changes for conntrack that have been
lying on the table for one week could be merged. But they are not ready
yet, they require another spin.
That means they'll have to wait until window opens again, they need
some extra time.
I'll stick to one pull request for bugfixes then.
Thanks!
prev parent reply other threads:[~2012-05-23 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 19:28 [README] Two merges pending David Miller
2012-05-23 10:45 ` Pablo Neira Ayuso [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=20120523104547.GA3312@1984 \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).