From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH common 2/3] cli handler: drop unused subroutine
Date: Fri, 5 Sep 2025 20:45:20 +0200 [thread overview]
Message-ID: <175709791980.1442697.7690409735812578719.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250812095637.444463-3-c.heiss@proxmox.com>
On Tue, 12 Aug 2025 11:56:26 +0200, Christoph Heiss wrote:
> This subroutine is never called anywhere, so drop it.
>
>
Applied, thanks!
[2/3] cli handler: drop unused subroutine
commit: 3b8c727ad1fc55ca0ea37e2af197e1a32b4fc4be
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-05 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:56 [pve-devel] [PATCH common/docs 0/5] fix #6656: add clickable anchors for cli subcommands Christoph Heiss
2025-08-12 9:56 ` [pve-devel] [PATCH common 1/3] gitignore: add rules for more build artifacts Christoph Heiss
2025-09-05 18:45 ` [pve-devel] applied: " Thomas Lamprecht
2025-08-12 9:56 ` [pve-devel] [PATCH common 2/3] cli handler: drop unused subroutine Christoph Heiss
2025-09-05 18:45 ` Thomas Lamprecht [this message]
2025-08-12 9:56 ` [pve-devel] [PATCH common 3/3] fix #6656: cli handler: generate anchors for all (sub-)commands Christoph Heiss
2025-09-05 18:45 ` [pve-devel] applied: " Thomas Lamprecht
2025-08-12 9:56 ` [pve-devel] [PATCH docs 4/5] fix #6656: asciidoc: add anchor links for paragraphs with ids Christoph Heiss
2025-09-05 19:06 ` [pve-devel] applied: " Thomas Lamprecht
2025-08-12 9:56 ` [pve-devel] [PATCH docs 5/5] update generated cli synopsis files Christoph Heiss
2025-09-05 19:06 ` 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=175709791980.1442697.7690409735812578719.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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