From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] i18n: bundle: mark git-bundle usage for translation
Date: Thu, 22 Jan 2015 13:10:35 +0600 [thread overview]
Message-ID: <CANCZXo4F8xWv4Z3_E281NHK3eAm-DChDCrjRCEoeO70T==+XAw@mail.gmail.com> (raw)
In-Reply-To: <xmqqiofzx2fi.fsf@gitster.dls.corp.google.com>
Ok, understand.
How to be with it? Resend after 2.3?
Thank you.
2015-01-22 3:13 GMT+06:00 Junio C Hamano <gitster@pobox.com>:
> Thanks, but please hold this off until the 2.3 final is tagged.
>
> It is way too late for anything that is not a regression fix at this
> point in this cycle, and changes that affect i18n are the last thing
> we want to take late in the cycle because l10n people need time to
> update the translations.
--
_________________________
0xAX
prev parent reply other threads:[~2015-01-22 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 19:03 [PATCH] i18n: bundle: mark git-bundle usage for translation Alexander Kuleshov
2015-01-21 21:13 ` Junio C Hamano
2015-01-22 7:10 ` Alexander Kuleshov [this message]
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='CANCZXo4F8xWv4Z3_E281NHK3eAm-DChDCrjRCEoeO70T==+XAw@mail.gmail.com' \
--to=kuleshovmail@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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 NNTP newsgroup(s).