From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Arturo Borrero Gonzalez <arturo@debian.org>,
Jeremy Sowden <jeremy@azazel.net>,
netfilter-devel@vger.kernel.org, fw@strlen.de
Subject: Re: [RFC] nftables 1.0.6 -stable backports
Date: Fri, 3 Nov 2023 16:02:30 +0100 [thread overview]
Message-ID: <ZUULhhY2E4H16IAd@orbyte.nwl.cc> (raw)
In-Reply-To: <ZUTZiB8xC1pVn+mn@calendula>
On Fri, Nov 03, 2023 at 12:29:12PM +0100, Pablo Neira Ayuso wrote:
> On Fri, Nov 03, 2023 at 11:56:52AM +0100, Phil Sutter wrote:
> > On Fri, Nov 03, 2023 at 11:49:30AM +0100, Pablo Neira Ayuso wrote:
> > > On Fri, Nov 03, 2023 at 11:44:43AM +0100, Phil Sutter wrote:
> > > > On Fri, Nov 03, 2023 at 10:59:25AM +0100, Phil Sutter wrote:
> > > > [...]
> > > > > One would have to change it to work based on *.y branches and the actual
> > > > > commits in there. I'll give it a quick try, shouldn't be too hard
> > > > > indeed.
> > > >
> > > > Please kindly find attached a "stable branch fork" of
> > > > collect_backports.sh. I was too lazy to check its output for missing
> > > > commits, but the ones it returns seem entirely valid.
> > >
> > > Would you mind to post the list of missing commits in 1.0.6.y?
> > >
> > > I am too lazy to run it.
> > >
> >
> > eac68b84227a3fc46572f3bae1113eaa91d13f24
>
> taken.
>
> > 8519ab031d8022999603a69ee9f18e8cfb06645d
>
> taken.
>
> > 4e8aa050312822400124260bf6b630c3c05cb04d
>
> taken.
>
> > f65b2d12236174d477c55e96c4027cd51185ba5e
>
> skipped for tests/shell.
>
> > 122dce6b35205a3df419a5cae9acfd6e83e8725a
>
> taken.
>
> These two below, I don't find in my tree (script woes!):
>
> > e4c9f9f7e0d1f83be18f6c4a418da503e9021b24
> > d392ddf243dcbf8a34726c777d2c669b1e8bfa85
Refresh your repo, these are the top two commits in nftables.git.
next prev parent reply other threads:[~2023-11-03 15:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 10:44 [RFC] nftables 1.0.6 -stable backports Pablo Neira Ayuso
2023-10-09 10:50 ` Florian Westphal
2023-10-09 11:05 ` Arturo Borrero Gonzalez
2023-10-09 11:15 ` Florian Westphal
2023-10-09 11:41 ` Pablo Neira Ayuso
2023-10-10 8:39 ` Phil Sutter
2023-10-10 10:37 ` Pablo Neira Ayuso
2023-10-10 13:30 ` Phil Sutter
2023-10-10 11:53 ` Jan Engelhardt
2023-10-10 15:24 ` Arturo Borrero Gonzalez
2023-10-09 11:44 ` Jeremy Sowden
2023-10-09 11:36 ` [RFC] nftables 0.9.8 " Pablo Neira Ayuso
2023-10-09 11:50 ` Jeremy Sowden
2023-10-10 8:54 ` Pablo Neira Ayuso
2023-10-10 20:08 ` Jeremy Sowden
2023-10-10 22:21 ` Pablo Neira Ayuso
2023-10-11 9:46 ` Jeremy Sowden
2023-10-11 10:01 ` Pablo Neira Ayuso
2024-02-17 20:11 ` Jeremy Sowden
2024-02-18 13:56 ` Jeremy Sowden
2023-10-11 8:01 ` [RFC] nftables 1.0.6 " Pablo Neira Ayuso
2023-10-11 15:25 ` Phil Sutter
2023-10-11 15:49 ` Pablo Neira Ayuso
2023-10-19 14:27 ` Pablo Neira Ayuso
2023-10-19 15:23 ` Phil Sutter
2023-11-02 11:34 ` Pablo Neira Ayuso
2023-11-02 12:27 ` Phil Sutter
2023-11-02 21:23 ` Pablo Neira Ayuso
2023-11-03 9:59 ` Phil Sutter
2023-11-03 10:44 ` Phil Sutter
2023-11-03 10:49 ` Pablo Neira Ayuso
2023-11-03 10:56 ` Phil Sutter
2023-11-03 11:29 ` Pablo Neira Ayuso
2023-11-03 12:11 ` Pablo Neira Ayuso
2023-11-03 15:02 ` Phil Sutter [this message]
2023-11-03 15:15 ` Pablo Neira Ayuso
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=ZUULhhY2E4H16IAd@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=arturo@debian.org \
--cc=fw@strlen.de \
--cc=jeremy@azazel.net \
--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;
as well as URLs for NNTP newsgroup(s).