From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Moayad Almalat <m.almalat@proxmox.com>
Subject: [pve-devel] applied: [PATCH i18n v2] update arabic translations
Date: Mon, 2 May 2022 14:44:33 +0200 [thread overview]
Message-ID: <d839bfb9-c82b-b072-b8bd-1b89b9213092@proxmox.com> (raw)
In-Reply-To: <20220502122103.390668-1-m.almalat@proxmox.com>
Am 5/2/22 um 14:21 schrieb Moayad Almalat:
> Signed-off-by: Moayad Almalat <m.almalat@proxmox.com>
> ---
> ar.po | 1199 ++++++++++++++++++++++++---------------------------------
> 1 file changed, 495 insertions(+), 704 deletions(-)
>
>
applied, thanks!
note that while this applied cleanly now, it missed a few changes from the last
`make update` run, I remerged it with the current state using `make do_update`,
which does all but the git submodule updates, so there are a few fuzzy entries
again (just fyi).
prev parent reply other threads:[~2022-05-02 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 12:21 [pve-devel] " Moayad Almalat
2022-05-02 12:44 ` 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=d839bfb9-c82b-b072-b8bd-1b89b9213092@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.almalat@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