From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
Mathieu Othacehe <m.othacehe@gmail.com>,
julien lepiller <roptat@lepiller.eu>
Subject: Re: Update on 1.0.1
Date: Fri, 17 May 2019 00:41:08 +0200 [thread overview]
Message-ID: <20190516224108.azsqjxmjf6idh4ec@pelzflorian.localdomain> (raw)
In-Reply-To: <20190516121302.atv7hestqgfv5qqg@pelzflorian.localdomain>
On Thu, May 16, 2019 at 02:13:02PM +0200, pelzflorian (Florian Pelz) wrote:
> On Thu, May 16, 2019 at 01:38:39PM +0200, Ludovic Courtès wrote:
> > I’ll create a ‘version-1.0.1’ branch with the aim of releasing the whole
> > thing maybe tomorrow or at least by Tuesday.
> >
>
> If this does not go through the TP, can we send a download link for a
> newer PO file adapted to current doc/guix.texi?
>
Please include this updated German PO file:
https://pelzflorian.de/guix-manual.de.po
It would be nice if a 1.0.1 POT file were published on the TP even if
it is not in time, so that the TP can again harbor the most current
translations.
Regards,
Florian
next prev parent reply other threads:[~2019-05-16 22:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 15:57 Update on 1.0.1 Ludovic Courtès
2019-05-09 16:35 ` znavko
2019-05-09 17:00 ` Giovanni Biscuolo
2019-05-14 11:57 ` Ludovic Courtès
2019-05-15 10:07 ` Giovanni Biscuolo
2019-05-09 17:45 ` Amin Bandali
2019-05-14 11:57 ` Ludovic Courtès
2019-05-15 13:16 ` Ludovic Courtès
2019-05-15 13:43 ` Mathieu Othacehe
2019-05-16 11:38 ` Ludovic Courtès
2019-05-16 12:13 ` pelzflorian (Florian Pelz)
2019-05-16 12:41 ` Miguel
2019-05-16 12:53 ` pelzflorian (Florian Pelz)
2019-05-16 13:02 ` Miguel
2019-05-16 22:41 ` pelzflorian (Florian Pelz) [this message]
2019-05-17 9:19 ` Ludovic Courtès
2019-05-17 9:55 ` pelzflorian (Florian Pelz)
2019-05-17 9:16 ` Ludovic Courtès
2019-05-17 13:02 ` Ricardo Wurmus
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=20190516224108.azsqjxmjf6idh4ec@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=m.othacehe@gmail.com \
--cc=roptat@lepiller.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.