From: Phil Sutter <phil@nwl.cc>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH] xshared: Accept an option if any given command allows it
Date: Thu, 24 Apr 2025 10:26:09 +0200 [thread overview]
Message-ID: <aAn1ofkNuxpohhaA@orbyte.nwl.cc> (raw)
In-Reply-To: <20250424100409.5f9ca598@gnosticus>
On Thu, Apr 24, 2025 at 10:04:09AM +1000, Adam Nielsen wrote:
> > > Hopefully it won't be too long until the next release, given the last
> > > one looks to have been a couple of years...
> >
> > Something between 6-12 months?
> >
> > v1.8.11: Wed Nov 6 11:47:59 2024 +0100
> > v1.8.10: Tue Oct 10 11:20:12 2023 +0200
> > v1.8.9: Tue Jan 10 17:46:43 2023 +0100
> > v1.8.8: Fri May 13 15:26:12 2022 +0200
> >
> > There's no rule though, we tend to release whenever there's "enough"
> > pending work. Right now we're just 14 commits in, I'd say we keep
> > collecting a bit more. :)
>
> Fair enough. I think the previous release sat in my distro's repos for
> around 18 months before we got 1.18.11, so I was hoping I wouldn't have
> to wait that long again before 1.18.12 comes along and gets my
> bandwidth monitoring scripts working again!
Which distribution are you using?
> I'll probably do a custom package with the git version, then I can get
> things going once more without hassling you for more frequent
> releases :)
Can't you file a ticket in downstream bug tracker and request a
backport? They probably also want commit 40406dbfaefbc ("nft: fix
interface comparisons in `-C` commands").
Cheers, Phil
next prev parent reply other threads:[~2025-04-24 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 12:19 [iptables PATCH] xshared: Accept an option if any given command allows it Phil Sutter
2025-04-23 21:09 ` Phil Sutter
2025-04-23 22:58 ` Adam Nielsen
2025-04-23 23:40 ` Phil Sutter
2025-04-24 0:04 ` Adam Nielsen
2025-04-24 8:26 ` Phil Sutter [this message]
2025-04-24 11:07 ` Adam Nielsen
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=aAn1ofkNuxpohhaA@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=a.nielsen@shikadi.net \
--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