netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@diku.dk>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developers <netfilter-devel@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	Solvik Blum <solvik.blum@smartjog.com>
Subject: Re: [RFC 0/3] MPEG2/TS drop analyzer iptables match extension
Date: Wed, 10 Nov 2010 12:02:20 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.1011081229390.13163@ask.diku.dk> (raw)
In-Reply-To: <alpine.LNX.2.01.1011041121170.16551@obet.zrqbmnf.qr>


On Thu, 4 Nov 2010, Jan Engelhardt wrote:
> On Thursday 2010-11-04 10:20, Jesper Dangaard Brouer wrote:
>> On Thu, 4 Nov 2010, Jan Engelhardt wrote:
>>>
>>> This now lives in the mp2t branch (since NFWS already actually) of xt-a,
>>> and I have taken the liberty to start updating it to higher standards.
>>> Please watch that branch, as I don't have any MPEG equipment around me
>>> to do runtime tests.
>>
>> Jan, I would actually like to maintain the source via my own git tree. And I
>> would gladly accept your patches against that tree.
>
> I do not mind who is hosting what parts, as git repos can be
> transferred easily, but I strongly suggest not to decouple xt_mp2t
> from (any clone of) the xtables-addons structure base, because doing
> so would bring you back to square one with regard to maintenance.
>
> I recognize you may dislike splitting up the IPTV codebase, so I
> propose that you make use of submodules, and have an Xt-a clone as
> one submodule. That would allow merging in both directions.

Well, I'm ready to maintain the module my self.  I know we talked (during 
Netfilter Workshop) about putting the module into the Xtables-addons 
git-tree, because the project had stalled.

But things have changed! - I now have some people/developers interested in 
the project, thus I'm taking an active maintainer role instead.

My plan is to keep the module "compatible" with the Xtables-addon build 
system.  Thats why I make my module use your compat_* system from xt-a.
This way you can easier copy the module into you tree, if I fail to 
maintain the module...

I have looked at your improvements in the "mp2t" branch of you tree. I'll 
integrate those changes/improvement in my tree, and give you the author 
credits in my tree.

(ps. this email got delayed on my postponed email outbox, sorry.  Have 
already had some offlist discussions with Jan)

Cheers,
   Jesper Brouer

--
-------------------------------------------------------------------
MSc. Master of Computer Science
Dept. of Computer Science, University of Copenhagen
Author of http://www.adsl-optimizer.dk
-------------------------------------------------------------------

      reply	other threads:[~2010-11-10 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 14:21 [RFC 0/3] MPEG2/TS drop analyzer iptables match extension Jesper Dangaard Brouer
2010-10-19 14:25 ` [RFC 1/3] MPEG2/TS drop analyzer file: xt_mp2t.h Jesper Dangaard Brouer
2010-10-19 14:26 ` [RFC 2/3] MPEG2/TS drop analyzer file: xt_mp2t.c Jesper Dangaard Brouer
2010-10-19 14:27 ` [RFC 3/3] MPEG2/TS drop analyzer file: libxt_mp2t.c Jesper Dangaard Brouer
2010-11-04  0:16 ` [RFC 0/3] MPEG2/TS drop analyzer iptables match extension Jan Engelhardt
2010-11-04  9:20   ` Jesper Dangaard Brouer
2010-11-04 10:29     ` Jan Engelhardt
2010-11-10 11:02       ` Jesper Dangaard Brouer [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=Pine.LNX.4.64.1011081229390.13163@ask.diku.dk \
    --to=hawk@diku.dk \
    --cc=eric.dumazet@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=solvik.blum@smartjog.com \
    /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).