From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Filip Schauer <f.schauer@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 manager 1/2] utils: clarify naming of LXC mount point utils
Date: Mon, 15 Apr 2024 14:12:42 +0200 [thread overview]
Message-ID: <61ef16aa-3e65-44de-be58-d429fafb5232@proxmox.com> (raw)
In-Reply-To: <20240131150317.128465-2-f.schauer@proxmox.com>
Am 31.01.24 um 16:03 schrieb Filip Schauer:
> Clarify the naming of mount point utils to clearly indicate their
> relation to LXC containers.
>
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
next prev parent reply other threads:[~2024-04-15 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 15:03 [pve-devel] [PATCH v3 manager 0/2] add edit window for device passthrough Filip Schauer
2024-01-31 15:03 ` [pve-devel] [PATCH v3 manager 1/2] utils: clarify naming of LXC mount point utils Filip Schauer
2024-04-15 12:12 ` Fiona Ebner [this message]
2024-01-31 15:03 ` [pve-devel] [PATCH v3 manager 2/2] ui: lxc: add edit window for device passthrough Filip Schauer
2024-04-15 12:12 ` Fiona Ebner
2024-04-16 11:48 ` Filip Schauer
2024-04-16 12:10 ` [pve-devel] [PATCH v3 manager 0/2] " Filip Schauer
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=61ef16aa-3e65-44de-be58-d429fafb5232@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.schauer@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