From: Vasco Almeida <vascomalmeida@sapo.pt>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2016, #02; Mon, 6)
Date: Tue, 7 Jun 2016 10:55:20 +0000 (UTC) [thread overview]
Message-ID: <loom.20160607T124159-111@post.gmane.org> (raw)
In-Reply-To: xmqqshwpsfor.fsf@gitster.mtv.corp.google.com
Junio C Hamano <gitster <at> pobox.com> writes:
> * va/i18n-even-more (2016-05-26) 22 commits
> - t5523: use test_i18ngrep for negation
[snip because of gmane]
> - i18n: advice: mark string about detached head for translation
> - i18n: builtin/remote.c: fix mark for translation
>
> More markings of messages for i18n, with updates to various tests
> to pass GETTEXT_POISON tests.
>
> Is everybody happy with this version?
I'm not. I've re-rolled this series, adding more patches on top of these and
have changed, for instance, patch "i18n: advice: mark string about detached
head for translation" which is the second one from down.
Also, I'm going to send yet another re-roll today (v4).
prev parent reply other threads:[~2016-06-07 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 5:58 What's cooking in git.git (Jun 2016, #02; Mon, 6) Junio C Hamano
2016-06-07 7:32 ` Mike Hommey
2016-06-07 7:37 ` Torsten Bögershausen
2016-06-07 10:55 ` Vasco Almeida [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=loom.20160607T124159-111@post.gmane.org \
--to=vascomalmeida@sapo.pt \
--cc=git@vger.kernel.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 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.