From: Friedrich Lobenstock <fl@fl.priv.at>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: latest pom: base/connlimit breaks kernel 2.4.25 compile (+possible fix)
Date: Sun, 11 Apr 2004 23:00:34 +0200 [thread overview]
Message-ID: <4079B1F2.8020007@fl.priv.at> (raw)
In-Reply-To: <Pine.LNX.4.44.0404112244380.21968-100000@filer.marasystems.com>
Henrik Nordstrom wrote on 11.04.2004 22:47 MET:
> On Sun, 11 Apr 2004, Friedrich Lobenstock wrote:
>
>
>>>I think the core people wants a patch to what currently is in pom-ng,
>>>replacing any earlier patches.
>>
>>Hmmmm....I am using plain pom, not pom-ng. So is this abandoned and not
>>maintained anymore?
>
>
> The development has fully switched over to pom-ng, and there will not be
> any new versions of the older pom published from what I can understand.
As far as I see there are still daily pom snapshots created so it
can't be dead.
> pom-ng contains a superset of the extensions which was found in pom.
How about stability pom compared to pom-ng? It was "only" released the
first time in March, so I think for the time beeing I will have to stay
with good old "normal" pom.
--
MfG / Regards
Friedrich Lobenstock
next prev parent reply other threads:[~2004-04-11 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 15:03 latest pom: base/connlimit breaks kernel 2.4.25 compile (+possible fix) Friedrich Lobenstock
2004-04-10 16:52 ` Pablo Neira
2004-04-10 19:17 ` Friedrich Lobenstock
2004-04-10 23:58 ` Henrik Nordstrom
2004-04-11 0:04 ` Friedrich Lobenstock
2004-04-11 10:39 ` Henrik Nordstrom
2004-04-11 11:17 ` Friedrich Lobenstock
2004-04-11 20:47 ` Henrik Nordstrom
2004-04-11 21:00 ` Friedrich Lobenstock [this message]
2004-04-12 2:16 ` Henrik Nordstrom
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=4079B1F2.8020007@fl.priv.at \
--to=fl@fl.priv.at \
--cc=netfilter-devel@lists.netfilter.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.