From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] libxtables: change option precedence order to be intuitive
Date: Mon, 15 Nov 2010 13:56:19 +0100 [thread overview]
Message-ID: <4CE12DF3.8050108@trash.net> (raw)
In-Reply-To: <1289824097-27337-1-git-send-email-jengelh@medozas.de>
On 15.11.2010 13:28, Jan Engelhardt wrote:
> The following changes since commit 648fd1ad68ae2ec675ac07efee80783912535404:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> libxt_TOS: avoid an undesired overflowing computation (2010-11-02 09:17:09 +0100)
>
> are available in the git repository at:
> git://dev.medozas.de/iptables master
Well, as I'm sure you're aware this doesn't apply to the
current tree, so please rebase.
next prev parent reply other threads:[~2010-11-15 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 12:28 [PATCH] libxtables: change option precedence order to be intuitive Jan Engelhardt
2010-11-15 12:28 ` [PATCH] iptables: fix longopt reecognition and workaround getopt(3) behavior Jan Engelhardt
2010-11-15 12:56 ` Patrick McHardy [this message]
2010-11-15 13:13 ` [PATCH] libxtables: change option precedence order to be intuitive Jan Engelhardt
2010-11-15 13:15 ` Patrick McHardy
2010-11-15 13:41 ` Jan Engelhardt
2010-11-15 13:46 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 15:16 iptables: option precedence order change Jan Engelhardt
2010-10-19 15:16 ` [PATCH] libxtables: change option precedence order to be intuitive Jan Engelhardt
2010-10-25 21:57 ` Jan Engelhardt
2010-10-28 9:54 ` Patrick McHardy
2010-10-28 10:54 ` Jan Engelhardt
2010-10-29 5:26 ` Changli Gao
2010-10-29 12:59 ` Jan Engelhardt
2010-10-29 17:04 ` Patrick McHardy
2010-11-15 10:38 ` Patrick McHardy
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=4CE12DF3.8050108@trash.net \
--to=kaber@trash.net \
--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 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).