All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Herz <andi@geekosphere.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Netfilter user mailing list <netfilter@vger.kernel.org>
Subject: Re: Formal submission of Xtables2
Date: Tue, 18 Dec 2012 15:09:57 +0100	[thread overview]
Message-ID: <20121218140957.GJ2606@workstation> (raw)
In-Reply-To: <alpine.LNX.2.01.1212141943060.16532@nerf07.vanv.qr>

On 14/12/12 at 19:49, Jan Engelhardt wrote:
> On Friday 2012-12-14 10:41, Andreas Herz wrote:
> >On 13/12/12 at 12:00, Pablo Neira Ayuso wrote:
> >> On Thu, Dec 13, 2012 at 07:00:07AM +0100, Jan Engelhardt wrote:
> >> [...]
> >> > Please consider for merging.
> >> 
> >> nftables and its compatibility layer already provide this and we will
> >> not have to maintain two different netlink interfaces, which is too
> >> much overhead.
> >
> >Apart of your discussion (i think it's quite interesting although you
> >might not agree), is there a summary of the status of nftables?
> >The last time i read about it, while i was at the university, i thought
> >it was dead.
> >I read that Patrick McHardy was the one pushing the project but never
> >heard any news after 2010. Now i read that Pablo is taking care of it.
> >
> >So i would love to hear more details on the roadmap for nftables, might
> >be interesting for me and my work here.
> 
> For parity, I am posting my roadmap document as it exists so far
> as well. Please see http://inai.de/nfxt/ .
> 
> And before the question of "who's maintaining?" coming up again -
> I'd be glad to maintain if only I was given the chance to.

Thanks so far for the informations. I will just see how the development
is going on and if i/we need some parts.

-- 
Andreas Herz

  reply	other threads:[~2012-12-18 14:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13  6:00 Formal submission of Xtables2 Jan Engelhardt
2012-12-13 11:00 ` Pablo Neira Ayuso
2012-12-13 11:36   ` Jan Engelhardt
2012-12-13 12:05     ` Pablo Neira Ayuso
2012-12-13 13:08       ` Jan Engelhardt
2012-12-13 14:28         ` Pablo Neira Ayuso
2012-12-13 14:53           ` Jan Engelhardt
2012-12-13 15:16             ` Pablo Neira Ayuso
2012-12-13 16:41               ` Jan Engelhardt
2012-12-13 17:25                 ` Pablo Neira Ayuso
2012-12-13 18:19                   ` Jan Engelhardt
2012-12-17  0:08                     ` Pablo Neira Ayuso
2012-12-17  1:39                       ` Jan Engelhardt
2012-12-17  9:53                         ` Pablo Neira Ayuso
2012-12-17 10:12                           ` Maciej Żenczykowski
2012-12-17 13:01                           ` Jan Engelhardt
2012-12-17 14:30                             ` Pablo Neira Ayuso
2012-12-17 20:51                               ` Jan Engelhardt
2012-12-17 23:49                                 ` Jozsef Kadlecsik
2012-12-18  1:11                                   ` Jan Engelhardt
2012-12-18  1:51                                     ` Neal Murphy
2012-12-18  1:27                                   ` David Miller
2012-12-14  9:41   ` Andreas Herz
2012-12-14 18:49     ` Jan Engelhardt
2012-12-18 14:09       ` Andreas Herz [this message]
2012-12-16 23:57     ` Pablo Neira Ayuso

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=20121218140957.GJ2606@workstation \
    --to=andi@geekosphere.org \
    --cc=jengelh@inai.de \
    --cc=netfilter@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.