From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Jesper Dangaard Brouer <hawk@diku.dk>, Ignacy Gawedzki <i@lri.fr>,
Netfilter Developers <netfilter-devel@vger.kernel.org>
Subject: Re: Netfilter API and libiptc
Date: Thu, 12 Feb 2009 06:58:25 +0100 [thread overview]
Message-ID: <4993BA81.8030404@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902120640480.32504@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2009-02-12 06:13, Patrick McHardy wrote:
>>> I have the code ready, it is easily mergeable-and-revertible(*) too, but let's
>>> wait with that because it currently relies on a certain revision of
>>> Makefile.am (IOW: merge conflicts with nf).
>>>
>>> (*) That is, changing it from 'lib_LTLIBRARIES' to 'noinst_LTLIBARIES' and it
>>> automatically becomes static wrt. the executables again. Oh I love automake :)
>> I'd prefer to wait until after the next release with this.
>
> I'd rather not want to wait another 4 months with this change
> [of enabling iptc to be installed].
> If Jesper then wants to play with the API, no problem, just
> don't forget bumping the so_version correctly.
>
>> We already have quite a few changes and missed the last release,
>
> Maybe releases should be more coordinated.
> I could come up with a big bunch of suggested guidelines upfront.
> Release-early-release-often is the one I miss most.
> .oO( and before I know it, I wrote another book )
If you write me a script to take care of all the website crap,
I'll happily release more often :) Its just a major PITA currently.
>> so I want to start stabilizing a nice new release for 2.6.29 soon.
>
> Here is your chance to make 1.4.3 nice - it does happen that some
> projects seem to use libiptc, and because it's not installed with
> distros because it is noinst_ in our happy Makefile.am, projects do a
> verbatim copy which a deed worse than having the current API -
> cherry-steal commit 1715851e now! :-D
I know. We've told them that this is a bad idea. Anyways, lets
see how intrusive these changes get.
next prev parent reply other threads:[~2009-02-12 5:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 14:17 Netfilter API and libiptc Ignacy Gawedzki
2009-02-09 17:10 ` Patrick McHardy
2009-02-09 18:39 ` Ignacy Gawedzki
2009-02-11 13:39 ` Jesper Dangaard Brouer
2009-02-11 14:37 ` Patrick McHardy
2009-02-11 16:02 ` Jan Engelhardt
2009-02-12 5:13 ` Patrick McHardy
2009-02-12 5:55 ` Jan Engelhardt
2009-02-12 5:58 ` Patrick McHardy [this message]
2009-02-12 6:14 ` Jan Engelhardt
2009-02-12 6:18 ` Patrick McHardy
2009-02-12 6:29 ` Jan Engelhardt
2009-02-12 6:34 ` Patrick McHardy
2009-02-16 13:08 ` Jesper Dangaard Brouer
2009-02-16 13:47 ` Jesper Dangaard Brouer
2009-02-16 14:08 ` Patrick McHardy
2009-02-16 16:52 ` Jan Engelhardt
2009-02-16 16:54 ` Patrick McHardy
2009-02-12 9:17 ` Jesper Dangaard Brouer
2009-02-12 10:42 ` Jesper Dangaard Brouer
2009-02-12 13:33 ` Ignacy Gawedzki
2009-02-12 14:11 ` Jan Engelhardt
2009-02-12 14:50 ` Jesper Dangaard Brouer
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=4993BA81.8030404@trash.net \
--to=kaber@trash.net \
--cc=hawk@diku.dk \
--cc=i@lri.fr \
--cc=jengelh@medozas.de \
--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).