From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Benno Schulenberg <coordinator@translationproject.org>,
Jochen Hein <jochen@jochen.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc 2.25 development --- 46 days to freeze.
Date: Sun, 20 Nov 2016 13:08:00 -0000 [thread overview]
Message-ID: <4a3bc644-4520-b58b-74f1-0514cac8e86e@gotplt.org> (raw)
In-Reply-To: <58318A3C.1050903@translationproject.org>
On Sunday 20 November 2016 05:04 PM, Benno Schulenberg wrote:
> The translators themselves don't use tarballs, they only use PO files.
> The TP extracts the POT files from a tarball, remerges the existing PO
> files at the TP against them, and delivers these newer PO files to the
> translators. Translators thus only need to have access to email and
> an editor -- nothing else. You want them to have git installed? And
> to know how to handle it? Sure, quite a few will know. But it would
> break their workflow, and mine.
>
> So, if it's not too much trouble, please keep providing a URL of a
> snapshot tarball on alpha.gnu.org (or somewhere else) and send that
> URL to the coordinator at the TP, so that I can just run my two or
> three scripts, and all runs smoothly.
Sure, it is no trouble at all. I only wanted to know if there was
interest in tweaking this workflow further than just generating libc.pot
multiple times. I am perfectly fine adapting to the existing workflow.
Siddhesh
next prev parent reply other threads:[~2016-11-20 13:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:55 Carlos O'Donell
2016-11-16 5:57 ` Jochen Hein
2016-11-20 4:40 ` Siddhesh Poyarekar
2016-11-20 6:11 ` Jochen Hein
2016-11-20 11:34 ` Benno Schulenberg
2016-11-20 13:08 ` Siddhesh Poyarekar [this message]
2016-12-01 13:32 ` Siddhesh Poyarekar
2016-12-01 16:03 ` Joseph Myers
2016-12-02 15:53 ` Carlos O'Donell
2016-12-02 15:57 ` Joseph Myers
2016-12-02 16:15 ` Carlos O'Donell
2016-12-02 15:54 ` Carlos O'Donell
2016-12-02 18:16 ` Siddhesh Poyarekar
2016-12-19 23:06 ` Carlos O'Donell
2016-12-20 16:54 ` Siddhesh Poyarekar
2016-12-02 18:18 ` Siddhesh Poyarekar
2016-12-19 14:24 ` Carlos O'Donell
2016-12-16 22:56 ` Mike Frysinger
2016-12-17 5:24 ` Siddhesh Poyarekar
2016-11-21 0:17 ` Nix
2016-11-22 18:58 ` Florian Weimer
2016-12-17 15:13 ` Zack Weinberg
2016-12-19 13:58 ` Carlos O'Donell
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=4a3bc644-4520-b58b-74f1-0514cac8e86e@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=coordinator@translationproject.org \
--cc=jochen@jochen.org \
--cc=libc-alpha@sourceware.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).