From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Jiang Xin <worldhello.net@gmail.com>
Subject: Re: [ANNOUNCE] Git v2.8.0-rc2
Date: Mon, 14 Mar 2016 08:56:34 -0700 [thread overview]
Message-ID: <xmqqoaahaw99.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <56E6D8C4.2010205@drmicha.warpmail.net> (Michael J. Gruber's message of "Mon, 14 Mar 2016 16:29:08 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Have you pulled git.pot for 2.8.0 already? [1]
Thanks for bringing this up.
No, I never pull the "git.pot round N for release" myself, as I am
not working on any translations, and I expect that translation teams
work off of i18n coordinator's tree (i.e. Jiang's tree), not from
mine. The updated git.pot would come to me along with the new
translations via his tree.
But if it makes it easier for translations teams and the i18n
coordinator to work together if I also pulled the git.pot update
myself, I'll do so. I just didn't know (and still don't know) if
that makes things easier for you guys, or if that risks making
things more confusing, having to or being able to pull from two
trees that are not necessarily in sync down to the minute.
> [1] http://permalink.gmane.org/gmane.comp.version-control.git/287774
next prev parent reply other threads:[~2016-03-14 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 23:04 [ANNOUNCE] Git v2.8.0-rc2 Junio C Hamano
2016-03-12 9:11 ` Max Horn
2016-03-14 18:10 ` Junio C Hamano
2016-03-14 15:29 ` Michael J Gruber
2016-03-14 15:30 ` [PATCH] wt-status: allow "ahead " to be picked up by l10n Michael J Gruber
2016-03-14 15:57 ` Junio C Hamano
2016-03-14 15:56 ` Junio C Hamano [this message]
2016-03-14 17:47 ` [ANNOUNCE] Git v2.8.0-rc2 Junio C Hamano
2016-03-16 13:33 ` Michael J Gruber
2016-03-16 13:40 ` Duy Nguyen
2016-03-16 15:32 ` Michael J Gruber
2016-03-16 16:30 ` Junio C Hamano
2016-03-17 14:51 ` Michael J Gruber
2016-03-17 15:14 ` [RFC/PATCH] Makefile: allow po generation through po target Michael J Gruber
2016-03-17 22:42 ` Junio C Hamano
2016-03-17 16:15 ` [ANNOUNCE] Git v2.8.0-rc2 Junio C Hamano
2016-03-20 9:45 ` Jiang Xin
2016-03-20 15:11 ` Michael J Gruber
2016-03-21 20:01 ` Junio C Hamano
2016-03-22 10:00 ` Michael J Gruber
2016-03-22 17:43 ` Junio C Hamano
2016-03-15 16:42 ` Jiang Xin
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=xmqqoaahaw99.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=worldhello.net@gmail.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 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.