From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH frr 1/2] debian: remove patch sequence numbers
Date: Wed, 25 Jun 2025 18:28:01 +0200 [thread overview]
Message-ID: <175086887646.988904.9368292173226050234.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250617162136.444316-1-g.goller@proxmox.com>
On Tue, 17 Jun 2025 18:21:35 +0200, Gabriel Goller wrote:
> Are not needed and we don't seem to add them usually on debian patches.
> Otherwise we'd need to increment on every new patch.
>
>
Applied, with some packaging/buildsys clean-ups on top, thanks!
[1/2] debian: remove patch sequence numbers
commit: 8efa19ad18b1f799957bcc5590e015ad213412c8
[2/2] frr: bump to 10.3.1
commit: 74de7c07084dab7fcf33cfbfa2b1eb8b767d231f
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-06-25 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 16:21 [pve-devel] " Gabriel Goller
2025-06-17 16:21 ` [pve-devel] [PATCH frr 2/2] frr: bump to 10.3.1 Gabriel Goller
2025-06-25 15:25 ` Hannes Duerr
2025-06-25 16:28 ` 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=175086887646.988904.9368292173226050234.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 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.