From: "rruegner" <robowarp@gmx.de>
To: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Cc: Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: [ANNOUNCE] call for testing of patch-o-matic-ng
Date: Wed, 25 Feb 2004 20:31:47 +0100 [thread overview]
Message-ID: <001101c3fbd6$0310ed80$32640a0a@robopc> (raw)
In-Reply-To: 20040225182828.GP13386@sunbeam.de.gnumonks.org
Hi Harald,
do you mean something like this ?
fresh 2.6.3 kernel with patch-o-matic-ng-20040224
Welcome to Patch-o-matic (1.13)!
Kernel: /usr/src/linux
Iptables: /usr/src/iptables
Each patch is a new feature: many have minimal impact, some do not.
Almost every one has bugs, so don't apply what you don't need!
-------------------------------------------------------
Already applied:
Not all requirements fulfilled for quake3-conntrack-nat, skipping:
requirement 'linux < 2.6.0' not fulfilled
Excellent! Source trees are ready for compilation.
your rewrite seems to work , but the h323 which i could compile in the past
was rejected too
is this current state of art ?
Regards Robert
----- Original Message -----
From: "Harald Welte" <laforge@netfilter.org>
To: "Netfilter Development Mailinglist"
<netfilter-devel@lists.netfilter.org>
Cc: "Netfilter Mailinglist" <netfilter@lists.netfilter.org>
Sent: Wednesday, February 25, 2004 7:28 PM
Subject: [ANNOUNCE] call for testing of patch-o-matic-ng
next prev parent reply other threads:[~2004-02-25 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 18:28 [ANNOUNCE] call for testing of patch-o-matic-ng Harald Welte
2004-02-25 19:31 ` rruegner [this message]
2004-02-25 20:28 ` Harald Welte
2004-02-26 16:00 ` RRuegner
2004-02-26 20:24 ` Henrik Nordstrom
2004-02-26 20:31 ` RRuegner
2004-02-26 20:28 ` call for testing of patch-o-matic-ng tested with kernel 2.4.25 failed for h323 RRuegner
2004-02-29 10:11 ` [ANNOUNCE] call for testing of patch-o-matic-ng Willy TARREAU
2004-02-29 10:25 ` Henrik Nordstrom
2004-02-29 13:33 ` Harald Welte
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='001101c3fbd6$0310ed80$32640a0a@robopc' \
--to=robowarp@gmx.de \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox