From: Satoshi Yasushima <s.yasushima@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Jakub Narębski" <jnareb@gmail.com>,
"Pat Thoyts" <patthoyts@users.sourceforge.net>,
"Satoshi Yasushima" <s.yasushima@gmail.com>
Subject: [PATCH v2 1/6] git-gui: consistently use the same word for "remote" in Japanese
Date: Wed, 7 Sep 2016 01:02:16 +0900 [thread overview]
Message-ID: <1473177741-9576-1-git-send-email-s.yasushima@gmail.com> (raw)
In-Reply-To: <1472913822-9088-1-git-send-email-s.yasushima@gmail.com>
Signed-off-by: Satoshi Yasushima <s.yasushima@gmail.com>
---
po/ja.po | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/po/ja.po b/po/ja.po
index 9aff249..8a2c16f 100644
--- a/po/ja.po
+++ b/po/ja.po
@@ -765,7 +765,8 @@ msgstr "トラッキング・ブランチを選択して下さい。"
#: lib/branch_create.tcl:140
#, tcl-format
msgid "Tracking branch %s is not a branch in the remote repository."
-msgstr "トラッキング・ブランチ %s は遠隔リポジトリのブランチではありません。"
+msgstr ""
+"トラッキング・ブランチ %s はリモートリポジトリのブランチではありません。"
#: lib/branch_create.tcl:153 lib/branch_rename.tcl:86
msgid "Please supply a branch name."
@@ -2192,7 +2193,7 @@ msgstr "%2$s にある %1$s をセットアップします"
#: lib/remote_branch_delete.tcl:29 lib/remote_branch_delete.tcl:34
msgid "Delete Branch Remotely"
-msgstr "遠隔でブランチ削除"
+msgstr "リモートブランチ削除"
#: lib/remote_branch_delete.tcl:47
msgid "From Repository"
@@ -2504,7 +2505,7 @@ msgstr "%s から新しい変更をフェッチしています"
#: lib/transport.tcl:18
#, tcl-format
msgid "remote prune %s"
-msgstr "遠隔刈込 %s"
+msgstr "リモート刈込 %s"
#: lib/transport.tcl:19
#, tcl-format
--
2.8.2.windows.1
next prev parent reply other threads:[~2016-09-06 16:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 14:43 [PATCH 1/6] git-gui: The term unified for remote in Japanese Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 2/6] git-gui: The term unified for blame " Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 4/6] git-gui: Add Japanese language code Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 5/6] git-gui: Update Japanese translation Satoshi Yasushima
2016-09-03 14:43 ` [PATCH 6/6] git-gui: Update Japanese information Satoshi Yasushima
2016-09-04 6:54 ` [PATCH 1/6] git-gui: The term unified for remote in Japanese Junio C Hamano
2016-09-05 16:32 ` Satoshi Yasushima
2016-09-04 12:10 ` Jakub Narębski
2016-09-05 17:16 ` Satoshi Yasushima
2016-09-05 18:03 ` Satoshi Yasushima
2016-09-06 16:02 ` Satoshi Yasushima [this message]
2016-09-06 16:02 ` [PATCH v2 2/6] git-gui: consistently use the same word for "blame" " Satoshi Yasushima
2016-09-06 16:02 ` [PATCH v2 4/6] git-gui: Add Japanese language code Satoshi Yasushima
2016-09-06 16:02 ` [PATCH v2 5/6] git-gui: Update Japanese translation Satoshi Yasushima
2016-09-06 16:02 ` [PATCH v2 6/6] git-gui: Update Japanese information Satoshi Yasushima
2016-09-07 11:47 ` Satoshi Yasushima
2016-09-07 17:35 ` Junio C Hamano
2016-09-08 6:59 ` git-gui, was " Johannes Schindelin
2016-09-08 16:48 ` Junio C Hamano
2016-09-20 13:37 ` Vasco Almeida
2016-09-21 18:16 ` Junio C Hamano
2016-09-26 14:21 ` Junio C Hamano
2016-09-08 12:55 ` Satoshi Yasushima
2016-10-03 8:45 ` Pat Thoyts
2016-10-03 16:18 ` Junio C Hamano
2016-10-03 19:31 ` Junio C Hamano
2016-10-03 23:07 ` Pat Thoyts
2016-10-04 1:20 ` 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=1473177741-9576-1-git-send-email-s.yasushima@gmail.com \
--to=s.yasushima@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=patthoyts@users.sourceforge.net \
/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.