From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Hannes Duerr <h.duerr@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 proxmox-i18n] update German translation
Date: Tue, 10 Oct 2023 11:07:12 +0200 [thread overview]
Message-ID: <57a309c1-6e96-4ba4-b2b5-bae4067d0935@proxmox.com> (raw)
In-Reply-To: <20231010074259.28301-1-h.duerr@proxmox.com>
Hi again,
On 10/10/23 09:42, Hannes Duerr wrote:
> update German translation
>
> Signed-off-by: Hannes Duerr <h.duerr@proxmox.com>
> ---
>
> Hab die Änderungen aufgenommen
not a blocker for this patch (so no need to send another version, as
this won't be visible in the commit message), but usually you'd write
something like this here:
Changes v2 -> v3:
- changed ...
- added ...
Changes v1 -> v2:
- changed ...
- removed ...
The format is not really standardized/important, as long the information
is there ;) It helps your colleagues when reviewing your (updated)
patches.
>
> de.po | 121 +++++++++++++++++++---------------------------------------
> 1 file changed, 40 insertions(+), 81 deletions(-)
>
--- SNIP 8< ---
--
- Lukas
next prev parent reply other threads:[~2023-10-10 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 7:42 Hannes Duerr
2023-10-10 9:07 ` Lukas Wagner [this message]
2023-10-10 10:46 ` [pve-devel] applied: " Thomas Lamprecht
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=57a309c1-6e96-4ba4-b2b5-bae4067d0935@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=h.duerr@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