public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: [pve-devel] applied:  [PATCH frr 0/2] Bump FRR to 10.4.1
Date: Wed, 26 Nov 2025 18:57:36 +0100	[thread overview]
Message-ID: <176417985250.998623.7257203370133530562.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251121141446.349501-1-g.goller@proxmox.com>

On Fri, 21 Nov 2025 15:13:21 +0100, Gabriel Goller wrote:
> Bump FRR to 10.4.1, we do this for two reasons:
>  * we can drop two patches, which have been merged upstream
>  * fix the libyang errors in the journal
>  * try to update a bit more frequently (maybe always one minor version behind
>    upstream would be nice), so that we can avoid the fallout of updating two
>    major versions (8->10) again.
> 
> [...]

Applied, thanks!

[1/2] bump frr to 10.4.1, remove obsolete patches
      commit: 03a2853fde15a4858916f56b61f070a0ac1410e0
[2/2] d/changelog: bump package version
      commit: 309200ce8202e9f9da46055594ee41b9ce840fa7


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-11-26 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 14:13 [pve-devel] " Gabriel Goller
2025-11-21 14:13 ` [pve-devel] [PATCH frr 1/2] bump frr to 10.4.1, remove obsolete patches Gabriel Goller
2025-11-21 14:13 ` [pve-devel] [PATCH frr 2/2] d/changelog: bump package version Gabriel Goller
2025-11-25 16:53 ` [pve-devel] [PATCH frr 0/2] Bump FRR to 10.4.1 DERUMIER, Alexandre via pve-devel
2025-11-26 12:59   ` Gabriel Goller
2025-11-26 16:00     ` Thomas Lamprecht
2025-11-26 17:57 ` Thomas Lamprecht [this message]

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=176417985250.998623.7257203370133530562.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=g.goller@proxmox.com \
    --cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal