From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager 0/3] Use Autoscaler instead of Autoscale on user-facing strings
Date: Tue, 12 Nov 2024 20:35:56 +0100 [thread overview]
Message-ID: <3d835834-e1e2-4e2f-a05a-169032bb3f17@proxmox.com> (raw)
In-Reply-To: <20231124130333.134501-1-m.sandoval@proxmox.com>
Am 24.11.23 um 14:03 schrieb Maximiliano Sandoval:
> The autoscaler is well-known Ceph concept. A translation might prefer to use
> "Autoscaler" as-is in a translation, which in turn lends itself better to a
> search online.
>
> The patch series is split into three commits since each one can be a bit more
> controvertial than the last one.
>
> Maximiliano Sandoval (3):
> ceph-pool: Add gettext to user-facing string
> ceph-pool: Replace PG Autoscale with PG Autoscaler on user-facing
> string
> ceph-pool: Replace Autoscale with Autoscaler in user-facing string
>
> www/manager6/ceph/Pool.js | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
applied series but squashed them into a single patch, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-12 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 13:03 [pve-devel] " Maximiliano Sandoval
2023-11-24 13:03 ` [pve-devel] [PATCH manager 1/3] ceph-pool: Add gettext to user-facing string Maximiliano Sandoval
2023-11-24 13:03 ` [pve-devel] [PATCH manager 2/3] ceph-pool: Replace PG Autoscale with PG Autoscaler on " Maximiliano Sandoval
2023-11-24 13:03 ` [pve-devel] [PATCH manager 3/3] ceph-pool: Replace Autoscale with Autoscaler in " Maximiliano Sandoval
2024-11-12 19:35 ` 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=3d835834-e1e2-4e2f-a05a-169032bb3f17@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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.