From: Fiona Ebner <f.ebner@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] ui: node: system: avoid using 'Syslog'
Date: Fri, 16 Feb 2024 08:58:52 +0100 [thread overview]
Message-ID: <b68be596-d2a9-4897-9162-922f9637f0f4@proxmox.com> (raw)
In-Reply-To: <901529669.2687.1708021517896@webmail.proxmox.com>
Am 15.02.24 um 19:25 schrieb Dietmar Maurer:
> I can also imaging using "Events" instead of "Syslog".
>
> - title: 'Syslog',
> + title: gettext('Events'),
>
> IMHO this is easier to translate.
>
Then at least "System Events". Otherwise it leaves the question "what
kind of events". And by far not all log messages correspond to events,
so IMHO this is worse.
next prev parent reply other threads:[~2024-02-16 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 12:59 Fiona Ebner
2024-02-15 18:20 ` Dietmar Maurer
2024-02-15 18:25 ` Dietmar Maurer
2024-02-16 7:58 ` Fiona Ebner [this message]
2024-02-16 7:56 ` Fiona Ebner
2024-02-16 8:29 ` Fiona Ebner
2024-02-16 9:01 ` Fabian Grünbichler
2024-02-16 9:22 ` Fiona Ebner
2024-02-16 9:25 ` Dietmar Maurer
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=b68be596-d2a9-4897-9162-922f9637f0f4@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=dietmar@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