From: Mike Frysinger <vapier@gentoo.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Jochen Hein <jochen@jochen.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc 2.25 development --- 46 days to freeze.
Date: Fri, 16 Dec 2016 22:56:00 -0000 [thread overview]
Message-ID: <20161216225620.GE30602@vapier.lan> (raw)
In-Reply-To: <94df0e62-72a0-dd24-ad85-0b2ee0b8eddc@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On 02 Dec 2016 10:54, Carlos O'Donell wrote:
> On 12/01/2016 08:32 AM, Siddhesh Poyarekar wrote:
> > On Wednesday 16 November 2016 11:26 AM, Jochen Hein wrote:
> >> Carlos O'Donell <carlos@redhat.com> writes:
> >>
> >>> We have 46 days of active development until the freeze for glibc 2.25 starts.
> >>
> >> Can we get a snapshot of the current pot-file out to the translators? We
> >> missed the last two releases, so I guess we need some time to catch up.
> >> We can (and should) refresh the pot file after the freeze to translate
> >> the last (hopefully few) messages before the release.
> >
> > Carlos, are you OK with me doing this or would there be any issues on
> > the glibc front that I am not aware of? If it is OK, I'll generate it
> > this weekend.
>
> I am perfectly OK with anyone helping with the release process.
can we automate this ? what if we add a cronjob that just uploads
the pot-file from master every two months ?
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-16 22:56 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
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 [this message]
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=20161216225620.GE30602@vapier.lan \
--to=vapier@gentoo.org \
--cc=carlos@redhat.com \
--cc=jochen@jochen.org \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).