From: Pablo Neira Ayuso <pablo@netfilter.org>
To: marty <martinbarrowcliff@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ulogd2 suggest
Date: Fri, 13 Jan 2012 15:28:33 +0100 [thread overview]
Message-ID: <20120113142833.GA21240@1984> (raw)
In-Reply-To: <4F0F6757.8090700@gmail.com>
On Thu, Jan 12, 2012 at 06:05:59PM -0500, marty wrote:
> Ulogd2 is NOT a prime-time candidate. Never has been.
> The API has been broken a long time.
> Too many issues unresolved.
Bah.
You don't even point to evindences. You don't even specify a
list of reasons why you affirm this or a list of unresolved
issues.
This is completely gratuitous.
> The wise way to fix the endian issues I documented are to use
> host byte order from the very beginning, as per my freely given patch.
Your patch breaks other plugins, I already told you. It's imcomplete.
If you change the endianness of the address, you have to propagate the
changes to other plugins.
[...]
> The database modules NEED to have more options in the config file,
> or a LOT of capabilities are unavailable. This is particular to
> each DBMS or DBI, so those need to be addressed individually.
Stop ranting, send patches.
This is a community project, if you feel something is broken, contribute
it, improve it and fix it, or if you don't know how to make it,
try to convince anyone to get it done. This is how it works.
So far, your overall contribution to the Netfilter project is ZERO
lines of code by now and tons of long emails with lots of complains.
Disregarding others is not the way to go, definitely not.
I'm very upset with your attitute, it's not coollaborative at all.
next prev parent reply other threads:[~2012-01-13 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 23:05 ulogd2 suggest marty
2012-01-13 7:40 ` Pierre Chifflier
2012-01-13 14:28 ` Pablo Neira Ayuso [this message]
2012-01-13 16:39 ` marty
2012-01-13 20:14 ` Pablo Neira Ayuso
2012-01-13 21:06 ` marty
2012-01-13 21:43 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2012-01-14 3:27 marty
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=20120113142833.GA21240@1984 \
--to=pablo@netfilter.org \
--cc=martinbarrowcliff@gmail.com \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).