public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Jiang Xin <worldhello.net@gmail•com>
Cc: "Git List" <git@vger•kernel.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail•com>,
	"Stefano Lattarini" <stefano.lattarini@gmail•com>
Subject: Re: [PATCH v2 0/7] i18n for git-am, git-rebase and git-merge
Date: Sun, 22 Jul 2012 12:47:19 -0700	[thread overview]
Message-ID: <7vmx2rr320.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: cover.1342920089.git.worldhello.net@gmail.com

Jiang Xin <worldhello.net@gmail•com> writes:

> Mark strings in git-am, git-rebase, and git-merge for translation.
> And contain fixes for shell gettext extraction and xgettext workaround.
>
> Jiang Xin (7):
>   i18n: New keywords for xgettext extraction from sh
>   i18n: rebase: mark strings for translation
>   i18n: Rewrite gettext messages start with dash
>   Remove obsolete LONG_USAGE which breaks xgettext
>   i18n: am: mark more strings for translation
>   Remove unused and bad gettext block from git-am
>   i18n: merge-recursive: mark strings for translation

I do not understand why many of these have Stefano's S-o-b in them.
If you are relaying what Stefano originally wrote, then the author
(i.e. "From: ") and the first S-o-b would say Stefano, and your
S-o-b will follow it, but that is probably not the case.

I'll drop the S-o-b lines for now.

By the way, is there any existing test that needs to gain GETTEXT_POISON
or test_i18ncmp with this change?

  parent reply	other threads:[~2012-07-22 19:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22  1:26 [PATCH v2 0/7] i18n for git-am, git-rebase and git-merge Jiang Xin
2012-07-22  1:26 ` [PATCH v2 1/7] i18n: New keywords for xgettext extraction from sh Jiang Xin
2012-07-22  1:26 ` [PATCH v2 2/7] i18n: rebase: mark strings for translation Jiang Xin
2012-07-22 19:04   ` Junio C Hamano
2012-07-22  1:26 ` [PATCH v2 3/7] i18n: Rewrite gettext messages start with dash Jiang Xin
2012-07-22  1:26 ` [PATCH v2 4/7] Remove obsolete LONG_USAGE which breaks xgettext Jiang Xin
2012-07-22  1:26 ` [PATCH v2 5/7] i18n: am: mark more strings for translation Jiang Xin
2012-07-22  1:26 ` [PATCH v2 6/7] Remove unused and bad gettext block from git-am Jiang Xin
2012-07-22  1:26 ` [PATCH v2 7/7] i18n: merge-recursive: mark strings for translation Jiang Xin
2012-07-22 19:37   ` Junio C Hamano
2012-07-22 19:47 ` Junio C Hamano [this message]
2012-07-23  3:14   ` [PATCH v2 0/7] i18n for git-am, git-rebase and git-merge Jiang Xin
2012-07-23  4:36     ` Junio C Hamano
2012-07-23  7:32       ` Jiang Xin
2012-07-23  7:38         ` Nguyen Thai Ngoc Duy
2012-07-23  8:01           ` 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=7vmx2rr320.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox$(echo .)com \
    --cc=avarab@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=pclouds@gmail$(echo .)com \
    --cc=stefano.lattarini@gmail$(echo .)com \
    --cc=worldhello.net@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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