git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] standardize usage strings that were missed the first time
Date: Fri, 3 Apr 2015 16:48:10 -0700	[thread overview]
Message-ID: <CAPc5daV7yf7X6y9-KAjGF2H=bq1T8gTR4729rDLFZtb-Pcs_TA@mail.gmail.com> (raw)
In-Reply-To: <CAMMLpeQkZ2jsuBg_J6veHpGcZiwwSzt+8xQ1g+dL2G18SnBtPw@mail.gmail.com>

On Fri, Apr 3, 2015 at 3:47 PM, Alex Henrie <alexhenrie24@gmail.com> wrote:
> 2015-04-02 15:56 GMT-06:00 Junio C Hamano <gitster@pobox.com>:
>> Thanks, but please no more _("string") changes for the rest of the
>> cycle, as that would impact i18n folks who will be starting from
>> tagged -rc releases.
>>
>> Please hold them off, and resend them after 2.4.0 final.
>
> I thought that during a code freeze, you held onto patches or
> committed them to a staging branch.

Yes, but that is done as time-permits basis, and it is much more
efficient to spread the load of remembering the topics that are
needed in future ;-)

Thanks.

  reply	other threads:[~2015-04-03 23:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 21:26 [PATCH] standardize usage strings that were missed the first time Alex Henrie
2015-04-02 21:56 ` Junio C Hamano
2015-04-03 22:47   ` Alex Henrie
2015-04-03 23:48     ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-02  3:12 Alex Henrie
2015-05-03 17:18 ` Junio C Hamano
2015-05-03 23:59   ` Junio C Hamano
2015-05-04 17:49     ` Alex Henrie
2015-05-04 19:23       ` Junio C Hamano

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='CAPc5daV7yf7X6y9-KAjGF2H=bq1T8gTR4729rDLFZtb-Pcs_TA@mail.gmail.com' \
    --to=gitster@pobox.com \
    --cc=alexhenrie24@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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 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).