public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	netdev@vger.kernel.org, Andreas Henriksson <andreas@fatal.se>,
	Yevgeny Kosarzhevsky <yevg@pisem.net>,
	Jan Engelhardt <jengelh@medozas.de>,
	Denys Fedoryschenko <denys@visp.net.lb>
Subject: Re: [PATCH] iproute2 : fix to catchup with xtables/iptables >= 1.4.2
Date: Mon, 26 Jan 2009 14:25:35 +0100	[thread overview]
Message-ID: <497DB9CF.6060408@trash.net> (raw)
In-Reply-To: <1232908352.13279.33.camel@dogo.mojatatu.com>

jamal wrote:
> Sorry for the long CC (copying all stakeholders)
> 
> Against latest iproute2 git - fixes breakage found with debian and
> certainly with any distro using iptables 1.4.2.
> 
> A small depart from the old ipt - to keep in sync with iptable/xtables
> changes. The old ipt should continue to work for iptables <1.4.1. And
> with this change, no old scripts will break.
>  
> [Breakage will happen again (probably by the time we hit iptables 1.4.3)
> because xtables is still a moving target. There are quiet a few
> functions which really should be part of xtables but are currently not -
> I have labelled them in tc/m_xt.c].

libxtables.so is pretty incomplete, the best thing would be if you'd
move everything you need there so we can avoid any breakage in the
future.

  reply	other threads:[~2009-01-26 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 18:32 [PATCH] iproute2 : fix to catchup with xtables/iptables >= 1.4.2 jamal
2009-01-26 13:25 ` Patrick McHardy [this message]
2009-01-26 13:47   ` jamal
2009-01-26 13:54     ` Patrick McHardy
2009-01-26 14:21       ` jamal
2009-01-26 14:24         ` Patrick McHardy
2009-01-26 14:27         ` Jan Engelhardt
2009-01-26 14:38           ` jamal
  -- strict thread matches above, loose matches on Subject: below --
2009-02-07 13:56 jamal
2009-02-07 14:43 ` Jan Engelhardt
2009-02-07 16:14   ` jamal

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=497DB9CF.6060408@trash.net \
    --to=kaber@trash.net \
    --cc=andreas@fatal.se \
    --cc=denys@visp.net.lb \
    --cc=hadi@cyberus.ca \
    --cc=jengelh@medozas.de \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=yevg@pisem.net \
    /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