From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Amin Vakil <info@aminvakil.com>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH widget-toolkit 1/1] fixes #4874: Improve VM Name error message
Date: Wed, 2 Aug 2023 10:16:12 +0200 [thread overview]
Message-ID: <0d690c4f-dca8-4651-b1c9-5df8792fd24d@proxmox.com> (raw)
In-Reply-To: <20230726153624.61608-2-info@aminvakil.com>
First thanks for this patch, such polishing are important contributions!
Am 26/07/2023 um 17:36 schrieb Amin Vakil:
please add the cover letter text to the commit message so that the context is
actually conserved in git history.
Also, for a simple single patch a cover letter is rather overhead, so you can
omit it there.
> Signed-off-by: Amin Vakil <info@aminvakil.com>
> ---
> src/Toolkit.js | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/Toolkit.js b/src/Toolkit.js
> index 67200c8..9dc28b9 100644
> --- a/src/Toolkit.js
> +++ b/src/Toolkit.js
> @@ -129,12 +129,12 @@ Ext.apply(Ext.form.field.VTypes, {
> DnsName: function(v) {
> return Proxmox.Utils.DnsName_match.test(v);
> },
> - DnsNameText: gettext('This is not a valid DNS name'),
> + DnsNameText: gettext('This is not a valid Host name'),
I'd not capitalize "Host" that looks odd here, it isn't an acronym after all.
Maybe even spell it together as "hostname", but no hard feelings on that part.
>
> DnsNameOrWildcard: function(v) {
> return Proxmox.Utils.DnsName_or_Wildcard_match.test(v);
> },
> - DnsNameOrWildcardText: gettext('This is not a valid DNS name'),
> + DnsNameOrWildcardText: gettext('This is not a valid Host name'),
same as above
>
> // email regex used by pve-common
> proxmoxMail: function(v) {
parent reply other threads:[~2023-08-02 8:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230726153624.61608-2-info@aminvakil.com>]
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=0d690c4f-dca8-4651-b1c9-5df8792fd24d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=info@aminvakil.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