public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Michael Köppl" <m.koeppl@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve_flutter_frontend 2/2] ui: make LXC containers naming more consistent
Date: Wed, 7 May 2025 10:12:04 +0200	[thread overview]
Message-ID: <ba135d7f-3513-4c16-8354-480babbd139e@proxmox.com> (raw)
In-Reply-To: <20250502121045.186346-2-m.koeppl@proxmox.com>

Am 02.05.25 um 14:10 schrieb Michael Köppl:
> To avoid confusion for users, consistent naming for LXC containers is
> applied. Since the main screen uses the plural "Virtual Machines", LXC
> containers is now also plural.
> 

Hmm, I do not have hard feelings for these things, but it _is_ a case
of the RAS syndrome [0], i.e. LXC already stands for Linux Containers.

FWIW, in the web UI we mostly write just Container(s), so maybe that
would be good enough for here too?

[0]: https://en.wikipedia.org/wiki/RAS_syndrome


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

  reply	other threads:[~2025-05-07  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 12:10 [pve-devel] [PATCH pve_flutter_frontend 1/2] fix typos Michael Köppl
2025-05-02 12:10 ` [pve-devel] [PATCH pve_flutter_frontend 2/2] ui: make LXC containers naming more consistent Michael Köppl
2025-05-07  8:12   ` Thomas Lamprecht [this message]
2025-05-09  7:20     ` Michael Köppl
2025-05-02 12:10 ` [pve-devel] [PATCH proxmox_dart_api_client 1/1] fix typos Michael Köppl
2025-05-07  8:09 ` [pve-devel] [PATCH pve_flutter_frontend 1/2] " Thomas Lamprecht
2025-05-09  8:41   ` Michael Köppl

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=ba135d7f-3513-4c16-8354-480babbd139e@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=m.koeppl@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