From: Translation Project Robot <robot@translationproject.org>
To: gcc-patches@gcc.gnu.org
Subject: Contents of PO file 'gcc-13.1.0.hr.po'
Date: Thu, 27 Apr 2023 21:07:10 +0200 [thread overview]
Message-ID: <E1ps6xS-0005sT-D5@duik.vrijschrift.org> (raw)
[-- Attachment #1: gcc-13.1.0.hr.po.gz --]
[-- Type: application/octet-stream, Size: 360573 bytes --]
[-- Attachment #2: Type: text/plain, Size: 209 bytes --]
The Translation Project robot, in the
name of your translation coordinator.
<coordinator@translationproject.org>
next reply other threads:[~2023-04-27 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 19:07 Translation Project Robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-01 17:32 Translation Project Robot
2023-05-07 3:07 Translation Project Robot
2023-05-06 2:57 Translation Project Robot
2023-04-27 18:07 Translation Project Robot
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=E1ps6xS-0005sT-D5@duik.vrijschrift.org \
--to=robot@translationproject.org \
--cc=gcc-patches@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).