From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager 1/2] pve8to9: lvm: use consistent spelling for autoactivation
Date: Tue, 29 Jul 2025 08:00:49 +0200 [thread overview]
Message-ID: <175376884058.3756942.2359009374339610096.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250728152400.972595-1-f.weber@proxmox.com>
On Mon, 28 Jul 2025 17:10:48 +0200, Friedrich Weber wrote:
> In some cases, autoactivation was spelled as "auto-activation". Remove
> the dash for consistency with other occurrences and the LVM
> documentation.
>
>
Applied, thanks!
[1/2] pve8to9: lvm: use consistent spelling for autoactivation
commit: 2e2ba120ee84087d6874d8e19a7b65497bc531f9
[2/2] pve8to9: lvm: fix missing space and remove unnecessary line break
commit: 0d02c18524079496c0914a54c81cf68a4489d45b
_______________________________________________
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-07-29 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:10 [pve-devel] " Friedrich Weber
2025-07-28 15:10 ` [pve-devel] [PATCH manager 2/2] pve8to9: lvm: fix missing space and remove unnecessary line break Friedrich Weber
2025-07-29 6:00 ` 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=175376884058.3756942.2359009374339610096.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.weber@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