From: Michael Renzmann <lartc@nospam.otaku42.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Contact for iptables-extension "ipp2p"?
Date: Mon, 10 May 2004 10:04:14 +0000 [thread overview]
Message-ID: <409F539E.20801@otaku42.de> (raw)
In-Reply-To: <409F11C5.2020203@otaku42.de>
Hi Andreas.
Andreas Klauer wrote:
> However, I also found two other projects which are pretty much capable of
> the same thing: iptables-p2p and l7-filter (both on Sourceforge). However,
> I haven't had the time for a closer look yet, so I don't know if they are
> any good.
I also found them before choosing ipp2p. But l7-filter is for kernel 2.6
only, and iptables-p2p seemed to be idle. So I decided to use ipp2p.
>>Question: is the contact address that is mentioned on the project
>>website still correct? If not, who should I contact?
> No idea - but not everyone reads his/her mail every day, so you probably
> should be more patient. Two weeks is not much time, especially if the
> author has to review a patch you wrote. I file some bug reports here and
> there (which should be read by more than one person only) and even there
> it sometimes takes months until I get a reply.
I know that people might be quite busy - I have the same problem. I was
just wondering if I took the wrong e-mail address, since answers to
questions regarding ipp2p here on the list have been answered very
quickly as far as I remember. Well, didn't meant to cause any trouble -
just been curious. :)
Bye, Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-05-10 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 5:23 [LARTC] Contact for iptables-extension "ipp2p"? Michael Renzmann
2004-05-10 8:53 ` Andreas Klauer
2004-05-10 10:04 ` Michael Renzmann [this message]
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=409F539E.20801@otaku42.de \
--to=lartc@nospam.otaku42.de \
--cc=lartc@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.