From: Eric Leblond <eric@inl.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Pierre Chifflier <chifflier@inl.fr>
Subject: Re: ulogd2 commit
Date: Sat, 18 Apr 2009 13:17:50 +0200 [thread overview]
Message-ID: <1240053470.10215.16.camel@ice-age> (raw)
In-Reply-To: <49E85F6D.9030008@netfilter.org>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
Hi,
Le vendredi 17 avril 2009 à 12:52 +0200, Pablo Neira Ayuso a écrit :
> Hi Eric, Pierre,
>
> Please, could you justify the need for commit
> 0ff525cb0506b2c043bc9df6d7e7b486c865bc38?
>
> http://git.netfilter.org/cgi-bin/gitweb.cgi?p=ulogd2.git;a=commit;h=0ff525cb0506b2c043bc9df6d7e7b486c865bc38
>
> I don't think that it's a good idea to support external compilation of
> ulogd2 modules. We should promote people to push forward things to mainline.
I clearly agree with the goal of promoting people to push forward things
to mainline but it has to be done by openness and reactivity of
mainteners, not by technical means.
But let looks at the diffstat of this commit:
include/Makefile.am | 1 +
include/ulogd/Makefile.am | 3 +--
include/ulogd/ulogd.h | 2 ++
3 files changed, 4 insertions(+), 2 deletions(-)
That's really not a big work for anyone to arrive to the same result. An
other point is that compiling outside of tree require you to maintain
your own build system which is quiet boring.
Thus, using git to maintain you own forked branch is the easiest way to
keep your work hidden and/or non public.
IMHO, this patch does not change anything about external contribution.
BR,
--
Eric Leblond <eric@inl.fr>
INL: http://www.inl.fr/
NuFW: http://www.nufw.org/
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-04-18 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 10:52 ulogd2 commit Pablo Neira Ayuso
2009-04-18 11:17 ` Eric Leblond [this message]
2009-04-18 11:43 ` Pablo Neira Ayuso
2009-04-18 11:58 ` Eric Leblond
2009-04-18 12:05 ` 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=1240053470.10215.16.camel@ice-age \
--to=eric@inl.fr \
--cc=chifflier@inl.fr \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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;
as well as URLs for NNTP newsgroup(s).