From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: xt_ecn revisited
Date: Tue, 27 Dec 2011 19:18:58 +0100 [thread overview]
Message-ID: <20111227181858.GA28674@1984> (raw)
In-Reply-To: <1324999681-22479-1-git-send-email-jengelh@medozas.de>
On Tue, Dec 27, 2011 at 04:27:56PM +0100, Jan Engelhardt wrote:
>
> fatal: Unable to look up (port 9418) (No address associated with hostname)
> warn: No branch of git://dev.medozas.de is at:
> warn: 806e172: netfilter: xtables: collapse conditions in xt_ecn
> warn: Are you sure you pushed HEAD there?
>
> The following changes since commit c5e1fd8ccae09f574d6f978c90c2b968ee29030c:
>
> Merge branch 'nf-next' of git://1984.lsi.us.es/net-next (2011-12-25 02:21:45 -0500)
>
> are available in the git repository at:
>
> git://dev.medozas.de ..BRANCH.NOT.VERIFIED..
>
> Jan Engelhardt (3):
> netfilter: xtables: move ipt_ecn to xt_ecn
> netfilter: xtables: give xt_ecn its own name
> netfilter: xtables: collapse conditions in xt_ecn
>
> Patrick McHardy (1):
> netfilter: xtables: add an IPv6 capable version of the ECN match
Is this Patrick's or you made a mistake here?
I don't find.
I'll try to pass this to davem by tomorrow, not sure if we'll reach the
merge window :-\
next prev parent reply other threads:[~2011-12-27 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 15:27 xt_ecn revisited Jan Engelhardt
2011-12-27 15:27 ` [PATCH 1/4] netfilter: xtables: move ipt_ecn to xt_ecn Jan Engelhardt
2011-12-27 15:27 ` [PATCH 2/4] netfilter: xtables: give xt_ecn its own name Jan Engelhardt
2011-12-27 15:27 ` [PATCH 3/4] netfilter: xtables: add an IPv6 capable version of the ECN match Jan Engelhardt
2011-12-27 15:28 ` [PATCH 4/4] netfilter: xtables: collapse conditions in xt_ecn Jan Engelhardt
2011-12-27 16:08 ` xt_ecn revisited Jan Engelhardt
2011-12-27 18:21 ` Pablo Neira Ayuso
2011-12-27 18:18 ` Pablo Neira Ayuso [this message]
2011-12-27 18:29 ` Jan Engelhardt
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=20111227181858.GA28674@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--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 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.