From: Jiang Xin <worldhello.net@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Please pull git-po master branch
Date: Wed, 2 May 2012 10:45:56 +0800 [thread overview]
Message-ID: <CANYiYbHtKKWw9LPnr+1khC5Oms-kOtA2WEucoNoE3Njzqiahzw@mail.gmail.com> (raw)
The following changes since commit 62bc83349d52be49b037d2c800a7f4064cfbc5b5:
The sixth batch of topics graduated to 'master' (2012-04-27 14:12:56 -0700)
are available in the git repository at:
https://github.com/git-l10n/git-po/ master
for you to fetch changes up to 839f7f8eed3bbb757dbbb6c2ef1a838974aa4bc8:
l10n: Update German translation (2012-05-02 07:46:35 +0800)
----------------------------------------------------------------
Byrial Jensen (2):
l10n: New da.po file with 0 translations
l10n: Add Danish team (da) to list of teams
Jiang Xin (8):
Merge master branch for tracking l10n updates of next release
l10n: Update git.pot (33 new, 24 deleted messages)
Merge maint branch for tracking l10n updates of git stable version
l10n: Update git.pot (2 new messages)
l10n: Update Simplified Chinese translation
Merge branch 'maint'
l10n: Update Simplified Chinese translation
Merge l10n updates from branch 'maint' into master
Marco Sousa (1):
l10n: Updated pt_PT language
Ralf Thielow (3):
l10n: Add the German translation team and initialize de.po
l10n: Initial German translation
l10n: Update German translation
po/TEAMS | 8 +
po/da.po | 3503 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
po/de.po | 3825 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
po/git.pot | 720 +++++------
po/pt_PT.po | 242 ++--
po/zh_CN.po | 783 ++++++------
6 files changed, 8271 insertions(+), 810 deletions(-)
create mode 100644 po/da.po
create mode 100644 po/de.po
next reply other threads:[~2012-05-02 2:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 2:45 Jiang Xin [this message]
2012-05-02 5:17 ` Please pull git-po master branch Junio C Hamano
2012-05-02 7:54 ` Thomas Rast
2012-05-02 9:13 ` Ralf Thielow
2012-05-02 13:58 ` Thomas Rast
2012-05-02 19:14 ` Ralf Thielow
2012-05-02 19:44 ` Christian Stimming
2012-05-02 13:49 ` [PATCH 0/5] de.po suggested updates Thomas Rast
2012-05-02 13:49 ` [PATCH 1/5] stash: make "saved" message translatable Thomas Rast
2012-05-02 16:42 ` Junio C Hamano
2012-05-02 13:49 ` [PATCH de.po 2/5] de.po: translate "bare" as "bloß" Thomas Rast
2012-05-02 13:49 ` [PATCH de.po 3/5] de.po: hopefully uncontroversial fixes Thomas Rast
2012-05-02 13:49 ` [PATCH de.po 4/5] de.po: translate "bad" as "ungültig" ("invalid") Thomas Rast
2012-05-02 13:49 ` [PATCH de.po 5/5] de.po: collection of suggestions Thomas Rast
2012-05-02 18:36 ` Ralf Thielow
2012-05-02 19:43 ` Thomas Rast
2012-05-02 19:42 ` Christian Stimming
2012-05-03 7:42 ` Thomas Rast
2012-05-03 13:12 ` [PATCH on ab/i18n] branch: remove lego in i18n tracking info strings Nguyễn Thái Ngọc Duy
2012-05-04 16:10 ` Junio C Hamano
2012-05-06 13:06 ` Nguyen Thai Ngoc Duy
2012-05-02 17:52 ` [PATCH 0/5] de.po suggested updates Ralf Thielow
2012-05-02 19:13 ` Christian Stimming
2012-05-02 16:40 ` Please pull git-po master branch Junio C Hamano
2012-05-03 4:31 ` Jiang Xin
2012-05-03 6:47 ` Junio C Hamano
2012-05-03 10:19 ` Jiang Xin
2012-05-03 7:49 ` Thomas Rast
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=CANYiYbHtKKWw9LPnr+1khC5Oms-kOtA2WEucoNoE3Njzqiahzw@mail.gmail.com \
--to=worldhello.net@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 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.