All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiang Xin <worldhello.net@gmail.com>
To: Junio C Hamano <gitster@pobox.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>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"Jiang Xin" <worldhello.net@gmail.com>
Subject: [PATCH v3 0/7] i18n for git-am, git-rebase and git-merge
Date: Tue, 24 Jul 2012 14:59:28 +0800	[thread overview]
Message-ID: <cover.1343112786.git.worldhello.net@gmail.com> (raw)

Marked messages for translation in git-am, git-rebase, and git-merge.
Also fixed affected test cases when turn GETTEXT_POISON switch on.

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

 Makefile                             |   3 +-
 git-am.sh                            |  14 ++--
 git-rebase.sh                        |  87 ++++++++------------
 git-submodule.sh                     |   2 +-
 merge-recursive.c                    | 148 +++++++++++++++++++----------------
 t/t3400-rebase.sh                    |   8 +-
 t/t3404-rebase-interactive.sh        |   2 +-
 t/t3406-rebase-message.sh            |   2 +-
 t/t6022-merge-rename.sh              |  16 ++--
 t/t6042-merge-rename-corner-cases.sh |   2 +-
 10 files changed, 134 insertions(+), 150 deletions(-)

-- 
1.7.12.rc0.17.gcb766d3

             reply	other threads:[~2012-07-24  7:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  6:59 Jiang Xin [this message]
2012-07-24  6:59 ` [PATCH v3 1/7] i18n: New keywords for xgettext extraction from sh Jiang Xin
2012-07-24  9:38   ` Stefano Lattarini
2012-07-24 17:46   ` Jonathan Nieder
2012-07-24  6:59 ` [PATCH v3 2/7] i18n: rebase: mark strings for translation Jiang Xin
2012-07-24  9:43   ` Stefano Lattarini
2012-07-24 18:01   ` Jonathan Nieder
2012-07-24 18:57     ` Junio C Hamano
2012-07-24 22:49     ` Jiang Xin
2012-07-24  6:59 ` [PATCH v3 3/7] i18n: Rewrite gettext messages start with dash Jiang Xin
2012-07-24  9:44   ` Stefano Lattarini
2012-07-24  6:59 ` [PATCH v3 4/7] Remove obsolete LONG_USAGE which breaks xgettext Jiang Xin
2012-07-24 18:08   ` Jonathan Nieder
2012-07-24 19:07     ` Junio C Hamano
2012-07-24  6:59 ` [PATCH v3 5/7] i18n: am: mark more strings for translation Jiang Xin
2012-07-24 18:16   ` Jonathan Nieder
2012-07-24 20:43     ` Junio C Hamano
2012-07-25  6:38       ` Thomas Rast
2012-07-24 23:00     ` Jiang Xin
2012-07-24  6:59 ` [PATCH v3 6/7] Remove unused and bad gettext block from git-am Jiang Xin
2012-07-24 18:27   ` Jonathan Nieder
2012-07-24 20:40     ` Junio C Hamano
2012-07-24 21:16     ` Martin von Zweigbergk
2012-07-24 21:21       ` Junio C Hamano
2012-07-24 21:25       ` Jonathan Nieder
2012-07-24 22:18         ` Junio C Hamano
2012-07-24  6:59 ` [PATCH v3 7/7] i18n: merge-recursive: mark strings for translation Jiang Xin
2012-07-24  9:47   ` Stefano Lattarini

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=cover.1343112786.git.worldhello.net@gmail.com \
    --to=worldhello.net@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --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 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.