From: Gabriel Goller <g.goller@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH frr 0/2] Bump FRR to 10.6.0
Date: Mon, 11 May 2026 10:58:37 +0200 [thread overview]
Message-ID: <diev4jgd64sro2rrlhbnoq5ea6e4fdxv2epnhgixehstcbtvz7@iaghmmko7jlh> (raw)
In-Reply-To: <xcncpfjidbaxqkrjtsun2u33u2amlyti5e6uubhyh7eh3xnrih@dnbpex732y3u>
On 08.05.2026 19:14, Gabriel Goller wrote:
> On 05.05.2026 14:26, Thomas Lamprecht wrote:
> > Am 05.05.26 um 11:36 schrieb Gabriel Goller:
> > > Note: 10.6.1 is out, so I will send a new version soon.
> > >
> > > We also need to backport:
> > > * https://github.com/FRRouting/frr/pull/21808
> > > * https://github.com/FRRouting/frr/pull/20005
> > >
> > After talking with Stefan I prepared now frr 10.6.1 with those PRs
> > cherry-picked and uploaded for internal QA, please cross check my
> > work in case I missed something.
>
> PR #20005 was merged, but not before some small stuff was changed. For
> completeness sake we should backport the new pr and release a -pve2 version
> probably?
Oof nevermind, the github diff between force pushes is broken?
Nothing changed between the applied PR and our patches.
Sorry for the noise.
> I will prepare that on monday and send a patch!
next prev parent reply other threads:[~2026-05-11 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 12:36 [PATCH frr 0/2] Bump FRR to 10.6.0 Gabriel Goller
2026-04-01 12:36 ` [PATCH frr 1/2] bump frr to 10.6.0, remove obsolete patch Gabriel Goller
2026-04-01 12:36 ` [PATCH frr 2/2] d/changelog: bump package version Gabriel Goller
2026-05-05 9:38 ` [PATCH frr 0/2] Bump FRR to 10.6.0 Gabriel Goller
2026-05-05 12:26 ` Thomas Lamprecht
2026-05-06 7:59 ` Gabriel Goller
2026-05-08 17:14 ` Gabriel Goller
2026-05-11 8:58 ` Gabriel Goller [this message]
2026-05-05 10:33 ` partially-applied: " Thomas Lamprecht
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=diev4jgd64sro2rrlhbnoq5ea6e4fdxv2epnhgixehstcbtvz7@iaghmmko7jlh \
--to=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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.