From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: pablo@netfilter.org,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: rfc: split libiptc linkage
Date: Mon, 08 Jun 2009 15:48:03 +0200 [thread overview]
Message-ID: <4A2D1693.5020202@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0906052127170.28126@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> as a result of a user inquiry thread posted to nf-dev earlier I
> produced this patch, but I am looking for some more justification to
> merge it. With it, ip(4)tables would only load ip4tc, and ip6tables
> only load ip6tc instead of both tools loading the current combined
> file libiptc.so. Since the combo file is just 47 KB I wonder whether the
> split is really worth the trouble.
> Opinions please.
I'd say let the user who requested it justify it :)
prev parent reply other threads:[~2009-06-08 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:33 rfc: split libiptc linkage Jan Engelhardt
2009-06-08 13:48 ` 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=4A2D1693.5020202@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--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 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.