All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Pablo Neira <pablo@eurodev.net>,
	KOVACS Krisztian <hidden@balabit.hu>
Subject: Re: [PATCH] Introducing the Change API
Date: Fri, 17 Dec 2004 18:26:43 +0100	[thread overview]
Message-ID: <41C316D3.1090604@trash.net> (raw)
In-Reply-To: <20041217080854.GC11436@sunbeam.de.gnumonks.org>

Harald Welte wrote:

>On Fri, Dec 17, 2004 at 06:28:55AM +0100, Patrick McHardy wrote:
>  
>
>>I would like to give it some cleanup first. Since it doesn't need to
>>deal with ipchains compatibility there is a lot possible cleanup.
>>I will probably do this in the next couple of weeks.
>>    
>>
>
>What kind of cleanup are you planning?  the provisions in conntrack are
>not that big for the compat stuff... it's more the provisions in nat
>(which we don't have yet for nf_conntrack).
>
Hmm I haven't looked into it very deeply yet, but I would like to kill
the nf_conntrack_standalone file and remove unneeded EXPORT_SYMBOLs.
I would also like to make naming more consistent and get rid of these
horrible long function names (nf_conntrack_do_something) by using the
nf_ct_ prefix everywhere.

>I'm willing to put some effort into this.  The question is:  Do we
>really need this cleanup before the merge, or can we do it afterwards?
>
>I mean, it seems to be stable - and it's not any more unclean than the
>current ip_conntrack code.  And we'll mark it as EXPERIMENTAL first
>anyway, so we have more freedom to play with it ;)
>  
>
Yes, but it's just less overhead doing this in your own tree than
submitting patches for all cleanups.

Regards
Patrick

      reply	other threads:[~2004-12-17 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 22:15 [PATCH] Introducing the Change API Pablo Neira
2004-12-05 20:23 ` Patrick McHardy
2004-12-16 12:40   ` Harald Welte
2004-12-16 12:53     ` KOVACS Krisztian
2004-12-16 15:34     ` Pablo Neira
2004-12-17  5:28     ` Patrick McHardy
2004-12-17  8:08       ` Harald Welte
2004-12-17 17:26         ` Patrick McHardy [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=41C316D3.1090604@trash.net \
    --to=kaber@trash.net \
    --cc=hidden@balabit.hu \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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.