Linux Netfilter development
 help / color / mirror / Atom feed
From: Duncan Roe <duncan_roe@optusnet.com.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: (re-send): Convert libnetfilter_queue to not need libnfnetlink]
Date: Sat, 13 Apr 2024 08:41:58 +1000	[thread overview]
Message-ID: <Zhm4tuJA6NQsh//4@slk15.local.net> (raw)
In-Reply-To: <Zgc6U4dPcoBeiFJy@calendula>

Hi Pablo,

On Fri, Mar 29, 2024 at 11:01:56PM +0100, Pablo Neira Ayuso wrote:
> Hi Duncan,
>
[SNIP]
>
> ... Then, document how to migrate from
> the old API to the new API, such documentation would be good to
> include a list of items with things that have changed between old and
> new APIs.

Waste of time I think. People are not going to migrate - what's in it for them?

*We* have to do the migration, because *we* then get to ditch libnfnetlink.

Over the years you have mentioned a desire to do that. Now it's done.
>
> Would you consider feasible to follow up in this direction? If so,
> probably you can make new API proposal that can be discussed.

Actually yes. It would make things easier for new users of libnetfilter_queue.
Will detail in another email.
>
> I hope this does not feel discouraging to you, I think all this work
> that you have done will be useful in this new approach and likely you
> can recover ideas from this patchset.
>
> Thanks for your patience.
>
Cheers ... Duncan.

PS Sorry if you got this twice - D

  parent reply	other threads:[~2024-04-12 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 21:31 (re-send): Convert libnetfilter_queue to not need libnfnetlink] Duncan Roe
2024-03-29 22:01 ` Pablo Neira Ayuso
2024-03-31 22:53   ` Duncan Roe
2024-04-12  5:35   ` (re-send): Convert libnetfilter_queue to not need libnfnetlink Duncan Roe
2024-04-12 22:41   ` Duncan Roe [this message]
2024-04-22  5:26   ` (re-send): Convert libnetfilter_queue to not need libnfnetlink] Duncan Roe

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=Zhm4tuJA6NQsh//4@slk15.local.net \
    --to=duncan_roe@optusnet.com.au \
    --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