diff --git a/po/documentation.zh_HANS-CN.po b/po/documentation.zh_HANS-CN.po
index ab89282d54f33baf8fda876caed4cc1e13f2b2b3..ebf3b2520426d73ad0669861130a9825e45317a5 100644
--- a/po/documentation.zh_HANS-CN.po
+++ b/po/documentation.zh_HANS-CN.po
@@ -3,7 +3,7 @@
 # This file is distributed under the same license as the Git package.
 # Matthias A횩hauer <mha1993@live.de>, 2019.
 msgid ""
-msgstr "Project-Id-Version: git documentation\nReport-Msgid-Bugs-To: jn.avila@free.fr\nPOT-Creation-Date: 2023-02-26 14:06+0100\nPO-Revision-Date: 2023-05-02 00:50+0000\nLast-Translator: Hou Qiyao <ryanhou24@gmail.com>\nLanguage-Team: LANGUAGE <LL@li.org>\nLanguage: zh_HANS-CN\nMIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit\nPlural-Forms: nplurals=1; plural=0;\nX-Generator: Weblate 4.18-dev\n"
+msgstr "Project-Id-Version: git documentation\nReport-Msgid-Bugs-To: jn.avila@free.fr\nPOT-Creation-Date: 2023-02-26 14:06+0100\nPO-Revision-Date: 2023-05-03 17:31+0000\nLast-Translator: 燁껃ㅄ��Ъ浴� <ttdlyu@163.com>\nLanguage-Team: LANGUAGE <LL@li.org>\nLanguage: zh_HANS-CN\nMIME-Version: 1.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit\nPlural-Forms: nplurals=1; plural=0;\nX-Generator: Weblate 4.18-dev\n"
 
 #. type: Labeled list
 #: en/blame-options.txt:1 en/diff-options.txt:769 en/git-instaweb.txt:45 en/git-mailinfo.txt:49 en/git-mailsplit.txt:35 en/git-repack.txt:146 en/git-status.txt:31
@@ -51969,49 +51969,49 @@ msgstr "���됧럴瀯뤸렌�졾댆榮℡폊訝�쉪�섇뙑�썰퓷�곩렅�룔��"
 #: en/git-stash.txt:207
 #, priority:240
 msgid "Interactively select hunks from the diff between HEAD and the working tree to be stashed.  The stash entry is constructed such that its index state is the same as the index state of your repository, and its worktree contains only the changes you selected interactively.  The selected changes are then rolled back from your worktree. See the ``Interactive Mode'' section of linkgit:git-add[1] to learn how to operate the `--patch` mode."
-msgstr ""
+msgstr "雅ㅴ틨凉뤷쑑餓롥퐪�띶늽��뭽藥δ퐳�뷰퉳�당쉪藥�펰訝��됪떓誤곩춼�①쉪�끻���  �뤷뙼�←쎅�꾣엫�졿삸瓦숁졆�꾬폏若껆쉪榮℡폊�뜻�곦툗鵝졽퍜佯볡쉪榮℡폊�뜻�곭쎑�뚳펽若껆쉪藥δ퐳�뷴룵�끻맜鵝졽벡雅믧�됪떓�꾢룜�뽧��  熬ラ�됦릎�꾡엶�밥폏餓롣퐷�꾢램鵝쒎뙷訝�썮譯싥�귛뢿鰲� linkgit:git-add[1] 訝�쉪 ``雅믣뒯與▼폀''訝��귨펽雅녻㎗倻귚퐬�띴퐳`--patch`與▼폀��"
 
 #. type: Plain text
 #: en/git-stash.txt:210
 #, priority:240
 msgid "The `--patch` option implies `--keep-index`.  You can use `--no-keep-index` to override this."
-msgstr ""
+msgstr "�됮」`---patch`�뤷뫑��`---keep-index`��  鵝졾룾餓δ슴��`--no-keep-index`�θ쫮�뽩츆��"
 
 #. type: Plain text
 #: en/git-stash.txt:218
 #, priority:240
 msgid "Stash only the changes that are currently staged. This is similar to basic `git commit` except the state is committed to the stash instead of current branch."
-msgstr ""
+msgstr "�ゅ춼�얍퐪�띶늽�뜻��꾡엶�밤�귟퓳映삡세雅롥읃�х쉪`git commit`竊뚦룵訝띹퓝��컛�뜻�곫룓雅ㅵ댆兀�뿈若ㅸ�뚥툖��퐪�띶늽����"
 
 #. type: Plain text
 #: en/git-stash.txt:220
 #, priority:240
 msgid "The `--patch` option has priority over this one."
-msgstr ""
+msgstr "`--patch`�됮」誤곦폍�덁틢瓦쇾릉�됮」��"
 
 #. type: Plain text
 #: en/git-stash.txt:223 en/git-stash.txt:233 en/git-stash.txt:247 en/git-stash.txt:252
 #, priority:240
 msgid "This option is only valid for `push` command."
-msgstr ""
+msgstr "瓦쇾릉�됮」�ゅ�`push`�썰빱�됪븞��"
 
 #. type: Plain text
 #: en/git-stash.txt:242
 #, priority:240
 msgid "This option is only valid for `apply`, `drop`, `pop`, `push`, `save`, `store` commands."
-msgstr ""
+msgstr "瓦쇾릉�됮」�ゅ�`apply`��`drop`��`pop`��`push`��`save`��`store`�썰빱�됪븞��"
 
 #. type: Plain text
 #: en/git-stash.txt:249
 #, priority:240
 msgid "Separates pathspec from options for disambiguation purposes."
-msgstr ""
+msgstr "訝뷰틙易덆솮閭㏛퉱竊뚦컛瓮�푶鰲꾥똽訝롩�됮」�녶���"
 
 #. type: Plain text
 #: en/git-stash.txt:257
 #, priority:240
 msgid "The new stash entry records the modified states only for the files that match the pathspec.  The index entries and working tree files are then rolled back to the state in HEAD only for these files, too, leaving files that do not match the pathspec intact."
-msgstr ""
+msgstr "�곁쉪兀�뿈�←쎅�よ�壤뺜틙寧�릦瓮�푶鰲꾥똽�뉏뻑�꾡엶�밭듁�곥��  �뜹릮榮℡폊�←쎅�뚦램鵝쒎뙷�뉏뻑阿잒˙�욄퍣�겼퐪�띶늽��릎�꾤듁�곻펽�ょ븰訝뗤툖寧�릦瓮�푶鰲꾥똽�꾣뻼餓뜰��"
 
 #. type: Labeled list
 #: en/git-stash.txt:260
@@ -52023,19 +52023,19 @@ msgstr "<stash>"
 #: en/git-stash.txt:263
 #, priority:240
 msgid "This option is only valid for `apply`, `branch`, `drop`, `pop`, `show` commands."
-msgstr ""
+msgstr "瓦쇾릉�됮」�ゅ�`apply`��`branch`��`drop`��`pop`��`show`�썰빱�됪븞��"
 
 #. type: Plain text
 #: en/git-stash.txt:266
 #, priority:240
 msgid "A reference of the form `stash@{<revision>}`. When no `<stash>` is given, the latest stash is assumed (that is, `stash@{0}`)."
-msgstr ""
+msgstr "訝�訝ゅ숱凉뤶맏`stash@{<�덃쑍>}`�꾢폊�ⓦ�귛쫩�쒏깹�됬퍢��`<兀�뿈窈�>`竊뚦닕�뉐츣����곁쉪�②뿈佯볩펷��`stash@{0}`竊됥��"
 
 #. type: Plain text
 #: en/git-stash.txt:275
 #, priority:240
 msgid "A stash entry is represented as a commit whose tree records the state of the working directory, and its first parent is the commit at `HEAD` when the entry was created.  The tree of the second parent records the state of the index when the entry is made, and it is made a child of the `HEAD` commit.  The ancestry graph looks like this:"
-msgstr ""
+msgstr "訝�訝よ눔�뤷틩�←쎅熬ヨ〃鹽뷰맏訝�訝ゆ룓雅ㅿ펽若껆쉪��퐬�묋�壤뺜틙藥δ퐳��퐬�꾤듁�곻펽若껆쉪寧т�訝ょ댍�귞궧��닗兩븃��←쎅�뜹쑉`HEAD`�꾣룓雅ㅳ��  寧т틠訝ょ댍�귞궧�꾣젒溫겼퐬雅녷씉��뵟�먩뿶榮℡폊�꾤듁�곻펽若껅삸`HEAD`�먧벡�꾡�訝ゅ춴�귞궧��  曄뽩뀍�양쐦壅룡씎�뤺퓳�뤄폏"
 
 #. type: Plain text
 #: en/git-stash.txt:279
@@ -52044,31 +52044,31 @@ msgid ""
 "            .----W\n"
 "           /    /\n"
 "     -----H----I\n"
-msgstr ""
+msgstr "            .----W\n           /    /\n     -----H----I\n"
 
 #. type: Plain text
 #: en/git-stash.txt:283
 #, priority:240
 msgid "where `H` is the `HEAD` commit, `I` is a commit that records the state of the index, and `W` is a commit that records the state of the working tree."
-msgstr ""
+msgstr "�뜸릎`H`��`HEAD`�먧벡竊�`I`���壤뺟뇨凉뺟듁�곭쉪�먧벡竊�`W`���壤뺝램鵝쒎뙷�뜻�곭쉪�먧벡��"
 
 #. type: Labeled list
 #: en/git-stash.txt:288
 #, no-wrap, priority:240
 msgid "Pulling into a dirty tree"
-msgstr ""
+msgstr "�됭퓵訝�訝よ꼷��퐬��"
 
 #. type: Plain text
 #: en/git-stash.txt:294
 #, priority:240
 msgid "When you are in the middle of something, you learn that there are upstream changes that are possibly relevant to what you are doing.  When your local changes do not conflict with the changes in the upstream, a simple `git pull` will let you move forward."
-msgstr ""
+msgstr "壤볞퐷�ⓨ걳�먧뻑雅뗧쉪�뜹�숋펽鵝졾풓�δ툓歷멩쐣訝�雅쎾룜�뽩룾�썰툗鵝졿��ⓨ걳�꾡틟�끾쐣�녈��  壤볞퐷�꾣쑍�겻엶�밥툗訝딀만�꾡엶�밥툖�꿰챳�띰펽訝�訝ょ��뺟쉪`git pull'弱긷룾餓θ�鵝좂빵瀯�뎺瓦쎼��"
 
 #. type: Plain text
 #: en/git-stash.txt:299
 #, priority:240
 msgid "However, there are cases in which your local changes do conflict with the upstream changes, and `git pull` refuses to overwrite your changes.  In such a case, you can stash your changes away, perform a pull, and then unstash, like this:"
-msgstr ""
+msgstr "�띈�뚳펽�ⓩ쐣雅쎿깄�듕툔竊뚥퐷�꾣쑍�겻엶�밭‘若욂툗訝딀만岳�뵻�됧넳囹곻펽��`git pull`�믥퍦誤녺썣鵝좂쉪岳�뵻��  �②퓳燁띷깄�듕툔竊뚥퐷��빳�듾퐷�꾥퓵佯╊퓷耶섋돈�ο펽�㎬죱訝�轝→땳�뽳펽�뜹릮�띹㎗凉�竊뚦깗瓦숁졆竊�"
 
 #. type: delimited block -
 #: en/git-stash.txt:307
@@ -52092,7 +52092,7 @@ msgstr ""
 #: en/git-stash.txt:315
 #, priority:240
 msgid "When you are in the middle of something, your boss comes in and demands that you fix something immediately.  Traditionally, you would make a commit to a temporary branch to store your changes away, and return to your original branch to make the emergency fix, like this:"
-msgstr ""
+msgstr "壤볞퐷閭ｅ쑉�싨윇餓뜸틟�꾣뿶�숋펽鵝좂쉪�곫씮�δ틙竊뚩쫨黎귚퐷塋뗥뜵岳�쨳�먧뻑雅뗣��  鴉좂퍨訝딉펽鵝졽폏�묇�訝や릿�뜹늽��룓雅ㅿ펽餓ε궓耶섆퐷�꾡엶�뱄펽�뜹릮瓦붷썮�겻퐷�꾢렅冶뗥늽��퓵烏뚨뇻�δ엶鸚랃펽弱긷깗瓦숁졆竊�"
 
 #. type: delimited block -
 #: en/git-stash.txt:326
@@ -52107,13 +52107,13 @@ msgid ""
 "$ git switch my_wip\n"
 "$ git reset --soft HEAD^\n"
 "# ... continue hacking ...\n"
-msgstr ""
+msgstr "# ... �③챺若� ...\n$ git switch -c my_wip\n$ git commit -a -m \"�묈푷鴉싪퓲孃쀥넍�밥툥蜈�\"\n$ git switch master\n$ edit emergency fix\n$ git commit -a -m \"�잓�잋엶鸚뛄UG\"\n$ git switch my_wip\n$ git reset --soft HEAD^\n# ... 瀯㎫뺌謠뉐뀯 ...\n"
 
 #. type: Plain text
 #: en/git-stash.txt:329
 #, priority:240
 msgid "You can use 'git stash' to simplify the above, like this:"
-msgstr ""
+msgstr "鵝졾룾餓η뵪'git stash'�η��뽨툓瓦겼램鵝쒙펽�뤺퓳�뤄폏"
 
 #. type: delimited block -
 #: en/git-stash.txt:337
@@ -52125,19 +52125,19 @@ msgid ""
 "$ git commit -a -m \"Fix in a hurry\"\n"
 "$ git stash pop\n"
 "# ... continue hacking ...\n"
-msgstr ""
+msgstr "# ... �③챺若� ...\n$ git stash\n$ edit emergency fix\n$ git commit -a -m \"榮㎪�δ엶鸚�\"\n$ git stash pop\n# ... 瀯㎫뺌謠뉐뀯 ...\n"
 
 #. type: Labeled list
 #: en/git-stash.txt:339
-#, no-wrap, priority:240
+#, fuzzy, no-wrap, priority:240
 msgid "Testing partial commits"
-msgstr ""
+msgstr "�ⓨ늽役뗨캊�먧벡"
 
 #. type: Plain text
 #: en/git-stash.txt:344
 #, priority:240
 msgid "You can use `git stash push --keep-index` when you want to make two or more commits out of the changes in the work tree, and you want to test each change before committing:"
-msgstr ""
+msgstr "壤볞퐷�녔뒍藥δ퐳�뷰툓�꾣뵻�ⓨ걳訝ㅴ릉�뽪쎍鸚싩쉪�먧벡竊뚦뭉訝붹꺍�ⓩ룓雅ㅵ뎺役뗨캊驪뤶릉�밧뒯�띰펽鵝졾룾餓δ슴��`git stash push --keep-index`竊�"
 
 #. type: delimited block -
 #: en/git-stash.txt:355
@@ -52152,19 +52152,19 @@ msgid ""
 "# ... repeat above five steps until one commit remains ...\n"
 "$ edit/build/test remaining parts\n"
 "$ git commit foo -m 'Remaining parts'\n"
-msgstr ""
+msgstr "# ... �③챺若� ...\n$ git add --patch foo # 餓끻컛寧т��ⓨ늽曆삣뒥�곁뇨凉뺜릎\n$ git stash push --keep-index # 弱녷��됧끀餓뽪뵻�ⓧ퓷耶섇댆�②뿈若ㅴ릎\n$ edit/build/test first part\n$ git commit -m '寧т�訝ら깿��' # �먧벡若뚦뀲役뗨캊瓦뉒쉪�밧뒯\n$ git stash pop # �녶쨭鸚꾤릤���됧끀餓뽪뵻��\n# ... �띶쨳餓δ툓雅붶릉閭ιい竊뚨쎍�겼돥訝뗤�訝ゆ룓雅�...\n$ 煐뽬풌/�꾢뻠/役뗨캊�⒳퐰�ⓨ늽\n$ git commit foo -m '�⒳퐰�ⓨ늽'��\n"
 
 #. type: Labeled list
 #: en/git-stash.txt:357
 #, no-wrap, priority:240
 msgid "Saving unrelated changes for future use"
-msgstr ""
+msgstr "岳앭춼訝띸쎑�녕쉪�섇뙑堊쎾컛�δ슴��"
 
 #. type: Plain text
 #: en/git-stash.txt:364
 #, priority:240
 msgid "When you are in the middle of massive changes and you find some unrelated issue that you don't want to forget to fix, you can do the change(s), stage them, and use `git stash push --staged` to stash them out for future use. This is similar to committing the staged changes, only the commit ends-up being in the stash and not on the current branch."
-msgstr ""
+msgstr "壤볞퐷�②퓵烏뚦ㄷ鰲꾣Æ岳�뵻�띰펽�묊렟訝�雅쎽툖�멨뀽�꾦뿮窯섓펽鵝졽툖�녑퓲溫겻엶鸚랃펽鵝졾룾餓θ퓵烏뚥엶�뱄펽弱녶끀�녽샄餘듸펽�뜹릮鵝욜뵪 `git stash push --staged` 弱녶끀耶섉붂壅룡씎竊뚥빳堊욕컛�δ슴�ⓦ�귟퓳映삡세雅롦룓雅ㅹ샄餘득�㏛엶�뱄펽�ゆ삸�먧벡�꾤퍜�쒏삸�②눔�뤷틩�뚥툖��쑉壤볟뎺�녷뵱��"
 
 #. type: delimited block -
 #: en/git-stash.txt:373
@@ -52177,19 +52177,19 @@ msgid ""
 "$ git commit -m 'Massive'       # commit fully tested changes\n"
 "$ git switch fixup-branch       # switch to another branch\n"
 "$ git stash pop                 # to finish work on the saved changes\n"
-msgstr ""
+msgstr "# ... �③챺若� ...\n$ git add --patch foo # 弱녵툖�멨뀽�꾣뵻�ⓩ렌�졾댆榮℡폊訝�\n$ git stash push --staged # 弱녻퓳雅쎿뵻�ⓧ퓷耶섇댆�②뿈佯볞릎\n# ... hack hack hack, finish curent changes ...\n$ git commit -m '鸚㎬쭊與→탩瑥�' # �먧벡若뚦뀲役뗨캊瓦뉒쉪�밧뒯\n$ git switch fixup-branch # �뉑뜟�겼룱訝�訝ゅ늽��\n$ git stash pop # 若뚧닇野밥퓷耶섊쉪岳�뵻�꾢램鵝�\n"
 
 #. type: Labeled list
 #: en/git-stash.txt:375
 #, no-wrap, priority:240
 msgid "Recovering stash entries that were cleared/dropped erroneously"
-msgstr ""
+msgstr "�℡쨳熬ラ뵗瑥�쑑歷낂솮/訝℡펱�꾥눔�뤷틩�←쎅"
 
 #. type: Plain text
 #: en/git-stash.txt:381
 #, priority:240
 msgid "If you mistakenly drop or clear stash entries, they cannot be recovered through the normal safety mechanisms.  However, you can try the following incantation to get a list of stash entries that are still in your repository, but not reachable any more:"
-msgstr ""
+msgstr "倻귝옖鵝좈뵗瑥�쑑訝℡펱�뽪툍�ㅴ틙兀�뿈佯볠씉��펽若껂뺄�졿퀡�싪퓝閭ｅ만�꾢츎�ⓩ쑛�뜻걿鸚띲��  �띈�뚳펽鵝졾룾餓θ캊瑥뺜툔�®쉪�믦�竊뚥빳�룟풓餓띶쑉鵝좂쉪�덃쑍佯볞릎竊뚥퐜�졿퀡�계씨�꾥눔�뤷틩�←쎅�쀨〃竊�"
 
 #. type: delimited block -
 #: en/git-stash.txt:386
@@ -52198,7 +52198,7 @@ msgid ""
 "git fsck --unreachable |\n"
 "grep commit | cut -d\\  -f3 |\n"
 "xargs git log --merges --no-walk --grep=WIP\n"
-msgstr ""
+msgstr "git fsck --unreachable |\ngrep commit | cut -d -f3 |\nxargs git log --merges --no-walk --grep=WIP\n"
 
 #. type: Plain text
 #: en/git-stash.txt:403
@@ -56267,61 +56267,61 @@ msgid ""
 "\t[--create-reflog] [--sort=<key>] [--format=<format>]\n"
 "\t[--merged <commit>] [--no-merged <commit>] [<pattern>...]\n"
 "'git tag' -v [--format=<format>] <tagname>...\n"
-msgstr ""
+msgstr "'git tag' [-a | -s | -u <��-id>] [-f] [-m <岳→겘> | -F <�뉏뻑>] [-e]\n\t<�뉒���> [<�먧벡> | <野배괌>]\n'git tag' -d <�뉒���>...\n'git tag' [-n[<�겼춻>]] -l [--contains <�먧벡>] [--no-contains <�먧벡>]\n\t[--points-at <野배괌>] [--column[=<�됮」>] | --no-column]\n\t[--create-reflog] [--sort=<��>] [--format=<�쇔폀>]\n\t[--merged <�먧벡>] [--no-merged <�먧벡>] [<與▼폀>...]\n'git tag' -v [--format=<format>] <�뉒���>...\n"
 
 #. type: Plain text
 #: en/git-tag.txt:26
 #, priority:240
 msgid "Add a tag reference in `refs/tags/`, unless `-d/-l/-v` is given to delete, list or verify tags."
-msgstr ""
+msgstr "��`refs/tags/`訝�렌�졽�訝ゆ젃嶺얍폊�⑨펽�ㅹ씆瀯쇿눣`-d/-l/-v`�ε닠�ㅳ�곩닓�뷸닑謠뚩칮�뉒���"
 
 #. type: Plain text
 #: en/git-tag.txt:28
 #, priority:240
 msgid "Unless `-f` is given, the named tag must not yet exist."
-msgstr ""
+msgstr "�ㅹ씆瀯쇿눣`-f`竊뚦맔�쇿뫝�띸쉪�뉒�恙낂』瓦섆툖耶섇쑉��"
 
 #. type: Plain text
 #: en/git-tag.txt:33
 #, priority:240
 msgid "If one of `-a`, `-s`, or `-u <key-id>` is passed, the command creates a 'tag' object, and requires a tag message.  Unless `-m <msg>` or `-F <file>` is given, an editor is started for the user to type in the tag message."
-msgstr ""
+msgstr "倻귝옖鴉좈�믢틙`-a', `-s', �� `-u <key-id>`訝�쉪訝�訝わ펽瑥ε뫝餓ㅴ폏�쎾뻠訝�訝�'�뉒�'野배괌竊뚦뭉誤곫콆�먧풘訝�訝ゆ젃嶺얌에����  �ㅹ씆瀯쇿눣`-m <岳→겘>`��`-F <�뉏뻑>`竊뚦맔�쇾폏��뒯訝�訝ょ폋渦묈솳竊뚩��ⓩ댎渦볟뀯�뉒�岳→겘��"
 
 #. type: Plain text
 #: en/git-tag.txt:36
 #, priority:240
 msgid "If `-m <msg>` or `-F <file>` is given and `-a`, `-s`, and `-u <key-id>` are absent, `-a` is implied."
-msgstr ""
+msgstr "倻귝옖瀯쇿츣雅�`-m <易덃겘>`��`-F <�뉏뻑>`竊뚦뭉訝붹깹��`-a`��`-s`��`-u <��-id>`竊뚦닕容섋�訝�`-a`��"
 
 #. type: Plain text
 #: en/git-tag.txt:39
 #, priority:240
 msgid "Otherwise, a tag reference that points directly at the given object (i.e., a lightweight tag) is created."
-msgstr ""
+msgstr "��닕竊뚦갚鴉싧닗兩뷰�訝ょ쎍�ζ뙁�묊퍢若싧�穩←쉪�뉒�凉뺟뵪竊덂뜵訝�訝よ슥�뤹벨�뉒�竊됥��"
 
 #. type: Plain text
 #: en/git-tag.txt:45
 #, priority:240
 msgid "A GnuPG signed tag object will be created when `-s` or `-u <key-id>` is used.  When `-u <key-id>` is not used, the committer identity for the current user is used to find the GnuPG key for signing. \tThe configuration variable `gpg.program` is used to specify custom GnuPG binary."
-msgstr ""
+msgstr "壤볞슴��`-s`��`-u <��-id>`�띰펽弱녶닗兩뷰�訝찱nuPG嶺얍릫�뉒�野배괌��  壤볠깹�됦슴��`-u <��-id>`�띰펽壤볟뎺�ⓩ댎�꾣룓雅ㅸ�낁벴餓썰폏熬ョ뵪�ε��퐾nuPG野녽뮙瓦쏂죱嶺얍릫�� \t�띸쉰�섌뇧 `gpg.program` �ⓧ틢�뉐츣�ゅ츣阿� GnuPG 雅뚩퓵�뜻뻼餓뜰��"
 
 #. type: Plain text
 #: en/git-tag.txt:51
 #, priority:240
 msgid "Tag objects (created with `-a`, `-s`, or `-u`) are called \"annotated\" tags; they contain a creation date, the tagger name and e-mail, a tagging message, and an optional GnuPG signature. Whereas a \"lightweight\" tag is simply a name for an object (usually a commit object)."
-msgstr ""
+msgstr "�뉒�野배괌竊덄뵪`-a`��`-s`��`-u`�쎾뻠竊됭˙燁겻맏 \"力③뇢 \"�뉒�竊쎾츆餓у똿�ュ닗兩뷸뿥�잆�곫젃溫계�끻쭞�띶뭽�드춴��뻑�곫젃溫겻에��뭽���됬쉪GnuPG嶺얍릫�귟�� \"饔삯뇧瀛� \"�뉒��ゆ삸訝�訝ゅ�穩∽펷�싧만���訝ゆ룓雅ㅵ�穩∽펹�꾢릫燁겹��"
 
 #. type: Plain text
 #: en/git-tag.txt:56
 #, priority:240
 msgid "Annotated tags are meant for release while lightweight tags are meant for private or temporary object labels. For this reason, some git commands for naming objects (like `git describe`) will ignore lightweight tags by default."
-msgstr ""
+msgstr "力③뇢�㎪젃嶺얏삸�ⓩ씎�묈툋�꾬펽�뚩슥�뤹벨�뉒��숁삸�ⓧ틢燁곦볶�뽨릿�뜹�穩←쉪�뉒��귞뵳雅롨퓳訝ゅ렅�좑펽訝�雅쎾뫝�띶�穩←쉪git�썰빱竊덂쫩`git describe`竊됮퍡溫ㅴ폏恙썹븼饔삯뇧瀛㎪젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:63
 #, priority:240
 msgid "Make an unsigned, annotated tag object"
-msgstr ""
+msgstr "�뜸퐳訝�訝ゆ뿞寧�뤇�곫쐣力③뇢�꾣젃嶺얍�穩�"
 
 #. type: Labeled list
 #: en/git-tag.txt:65
@@ -56333,7 +56333,7 @@ msgstr "--sign"
 #: en/git-tag.txt:70
 #, priority:240
 msgid "Make a GPG-signed tag, using the default e-mail address's key.  The default behavior of tag GPG-signing is controlled by `tag.gpgSign` configuration variable if it exists, or disabled otherwise.  See linkgit:git-config[1]."
-msgstr ""
+msgstr "�뜸퐳訝�訝찱PG嶺얍릫�꾣젃嶺억펽鵝욜뵪容섋��드춴��뻑�겼��꾢칳�γ��  �뉒�GPG嶺얍릫�꾦퍡溫ㅸ죱訝븀뵳`tag.gpgSign`�띸쉰�섌뇧�㎩댍竊덂쫩�쒎춼�⑨펹竊뚦맔�숂쫨�ⓦ��  �귟쭅 linkgit:git-config[1]��"
 
 #. type: Labeled list
 #: en/git-tag.txt:71
@@ -56345,7 +56345,7 @@ msgstr "--no-sign"
 #: en/git-tag.txt:74
 #, priority:240
 msgid "Override `tag.gpgSign` configuration variable that is set to force each and every tag to be signed."
-msgstr ""
+msgstr "誤녺썣`tag.gpgSign`�띸쉰�섌뇧竊뚩��섌뇧熬ヨ�營�맏凉뷴댍驪뤶�訝ゆ젃嶺얗꺗熬ョ��띲��"
 
 #. type: Labeled list
 #: en/git-tag.txt:75
@@ -56364,25 +56364,25 @@ msgstr "--�믣틣=<��>"
 #: en/git-tag.txt:78
 #, priority:240
 msgid "Make a GPG-signed tag, using the given key."
-msgstr ""
+msgstr "�뜸퐳訝�訝찱PG嶺얍릫�꾣젃嶺억펽鵝욜뵪瀯쇿츣�꾢칳�γ��"
 
 #. type: Plain text
 #: en/git-tag.txt:82
 #, priority:240
 msgid "Replace an existing tag with the given name (instead of failing)"
-msgstr ""
+msgstr "�①퍢若싩쉪�띸㎞�욘뜟訝�訝ょ렟�됬쉪�뉒�竊덅�뚥툖��ㅁ兀ο펹"
 
 #. type: Plain text
 #: en/git-tag.txt:86
 #, priority:240
 msgid "Delete existing tags with the given names."
-msgstr ""
+msgstr "�좈솮瀯쇿츣�띶춻�꾤렟耶섉젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:90
 #, priority:240
 msgid "Verify the GPG signature of the given tag names."
-msgstr ""
+msgstr "謠뚩칮瀯쇿츣�뉒��띸㎞�껯PG嶺얍릫��"
 
 #. type: Labeled list
 #: en/git-tag.txt:91
@@ -56394,85 +56394,85 @@ msgstr "-n<num>"
 #: en/git-tag.txt:94
 #, priority:240
 msgid "<num> specifies how many lines from the annotation, if any, are printed when using -l. Implies `--list`."
-msgstr ""
+msgstr "<�겼춻>�뉐츣�ⓧ슴��-l�뜻돀�겼쩀弱묋죱力③뇢竊�-l��뙁\"--list\"��"
 
 #. type: Plain text
 #: en/git-tag.txt:98
 #, priority:240
 msgid "The default is not to print any annotation lines.  If no number is given to `-n`, only the first line is printed.  If the tag is not annotated, the commit message is displayed instead."
-msgstr ""
+msgstr "容섋���툖�볟뜲餓삡퐬力③뇢烏뚣��  倻귝옖亦→쐣瀯� `n `�졽툓�겼춻竊뚦닕�ゆ돀�곁К訝�烏뚣��  倻귝옖�뉒�亦→쐣力③뇢竊뚦닕鴉싨샑鹽뷸룓雅ㅴ에����"
 
 #. type: Plain text
 #: en/git-tag.txt:103
 #, ignore-ellipsis, priority:240
 msgid "List tags. With optional `<pattern>...`, e.g. `git tag --list 'v-*'`, list only the tags that match the pattern(s)."
-msgstr ""
+msgstr "�쀥눣�뉒��귚슴�ⓨ룾�됬쉪`<與▼폀>...`竊뚥풃倻�`git tag --list 'v-*'`竊뚦룵�쀥눣寧�릦與▼폀�꾣젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:107
 #, priority:240
 msgid "Running \"git tag\" without arguments also lists all tags. The pattern is a shell wildcard (i.e., matched using fnmatch(3)). Multiple patterns may be given; if any of them matches, the tag is shown."
-msgstr ""
+msgstr "瓦먫죱 \"git tag \"�뜸툖�졾뢿�겻튋鴉싧닓�뷸��됪젃嶺얇�귝Æ凉뤸삸訝�訝챪hell�싮뀓寧�펷�녕뵪fnmatch(3)�백뀓竊됥�귛룾餓η퍢�뷴쩀訝ゆÆ凉륅폑倻귝옖�뜸릎餓삡퐬訝�訝ゅ뙶�랃펽弱긴폏�양ㅊ瑥ζ젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:111
 #, priority:240
 msgid "This option is implicitly supplied if any other list-like option such as `--contains` is provided. See the documentation for each of those options for details."
-msgstr ""
+msgstr "倻귝옖�먧풘餓삡퐬�뜸퍟映삡세�쀨〃�꾦�됮」竊뚦쫩`--contains`竊뚦닕�먨맜�경룓堊쏂��됮」�귟��낁��귟쭅瓦쇾틳�됮」�꾣뻼旅ｃ��"
 
 #. type: Plain text
 #: en/git-tag.txt:124
 #, priority:240
 msgid "Sort based on the key given.  Prefix `-` to sort in descending order of the value. You may use the --sort=<key> option multiple times, in which case the last key becomes the primary key. Also supports \"version:refname\" or \"v:refname\" (tag names are treated as versions). The \"version:refname\" sort order can also be affected by the \"versionsort.suffix\" configuration variable.  The keys supported are the same as those in `git for-each-ref`.  Sort order defaults to the value configured for the `tag.sort` variable if it exists, or lexicographic order otherwise. See linkgit:git-config[1]."
-msgstr ""
+msgstr "�방뜮瀯쇿츣�꾦뵰瓦쏂죱�믣틣��  �띸�\"-\"烏①ㅊ�됬뀱�겼�쇘쉪�띶틣�믣틣�귚퐷��빳鸚싨А鵝욜뵪--sort=<��>�됮」竊뚦쑉瓦숂쭕�끻넻訝뗰펽���롣�訝ら뵰�먧맏訝삯뵰�귚튋��똻 \"version:refname \"�� \"v:refname\"竊덃젃嶺얍릫熬ヨ쭍訝븀뎵�э펹��\"version:refname \"�꾣럲佯뤻『佯뤶튋��빳�� \"versionort.senffix \"�띸쉰�섌뇧壤긷뱧��  ��똻�꾦뵰訝�`git for-each-ref`訝�쉪�멨릪��  �믣틣窈뷴틣容섋�訝� \"tag.sort \"�섌뇧�꾦뀓營��쇽펷倻귝옖耶섇쑉�꾥캕竊됵펽��닕訝븃칾力뺡『佯뤵�귟쭅linkgit:git-config[1]��"
 
 #. type: Plain text
 #: en/git-tag.txt:133
 #, priority:240
 msgid "Sorting and filtering tags are case insensitive."
-msgstr ""
+msgstr "�믣틣�뚩퓝譯ㅶ젃嶺얌툖�뷴늽鸚㎩컦�쇻��"
 
 #. type: Plain text
 #: en/git-tag.txt:139
 #, priority:240
 msgid "Display tag listing in columns. See configuration variable `column.tag` for option syntax. `--column` and `--no-column` without options are equivalent to 'always' and 'never' respectively."
-msgstr ""
+msgstr "�ⓨ닓訝�샑鹽뷸젃嶺얍닓烏ⓦ�귡�됮」瑥�퀡鰲곲뀓營�룜��`column.tag`��`--column`��`--no-column`亦→쐣�됮」竊뚦늽�ョ춬�뚥틢'麗멱퓶'��'餓롣툖'��"
 
 #. type: Plain text
 #: en/git-tag.txt:141
 #, priority:240
 msgid "This option is only applicable when listing tags without annotation lines."
-msgstr ""
+msgstr "瓦쇾릉�됮」�ら�귞뵪雅롥닓�뷸깹�됪낏�딁봇�꾣젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:145
 #, priority:240
 msgid "Only list tags which contain the specified commit (HEAD if not specified). Implies `--list`."
-msgstr ""
+msgstr "�ゅ닓�뷴똿�ユ뙁若싨룓雅ㅵ냵若밭쉪�뉒�竊덂쫩�쒏깹�됪뙁若싧닕訝뷴퐪�띶늽��펹�귝슅��`--list`��"
 
 #. type: Plain text
 #: en/git-tag.txt:149
 #, priority:240
 msgid "Only list tags which don't contain the specified commit (HEAD if not specified). Implies `--list`."
-msgstr ""
+msgstr "�ゅ닓�뷴똿�ユ뙁若싨룓雅ㅵ냵若밭쉪�뉒�竊덂쫩�쒏깹�됪뙁若싧닕訝뷴퐪�띶늽��펹�귝슅��`--list`��"
 
 #. type: Plain text
 #: en/git-tag.txt:153
 #, priority:240
 msgid "Only list tags whose commits are reachable from the specified commit (`HEAD` if not specified)."
-msgstr ""
+msgstr "�ゅ닓�뷴끀�먧벡��빳餓롦뙁若싨룓雅ㅿ펷倻귝옖亦→쐣�뉐츣�쇾맏`HEAD`竊됧댆渦양쉪�뉒���"
 
 #. type: Plain text
 #: en/git-tag.txt:157
 #, priority:240
 msgid "Only list tags whose commits are not reachable from the specified commit (`HEAD` if not specified)."
-msgstr ""
+msgstr "�ゅ닓�뷴끀�먧벡��빳餓롦뙁若싨룓雅ㅿ펷倻귝옖亦→쐣�뉐츣�쇾맏`HEAD`竊됧댆渦양쉪�뉒���"
 
 #. type: Plain text
 #: en/git-tag.txt:161
 #, priority:240
 msgid "Only list tags of the given object (HEAD if not specified). Implies `--list`."
-msgstr ""
+msgstr "�ゅ닓�븀퍢若싧�穩←쉪�뉒�竊덂쫩�쒏깹�됪뙁若싧닕訝뷴퐪�띶늽��펹�귝슅��`--list`��"
 
 #. type: Plain text
 #: en/git-tag.txt:169
@@ -56492,25 +56492,25 @@ msgstr "餓롧퍢若싨뻼餓뜸릎�룟룚�먧벡岳→겘��  鵝욜뵪'-'��빳餓롦젃�녻풏��
 #: en/git-tag.txt:182
 #, priority:240
 msgid "The message taken from file with `-F` and command line with `-m` are usually used as the tag message unmodified.  This option lets you further edit the message taken from these sources."
-msgstr ""
+msgstr "��`-F`餓롦뻼餓뜸릎�룟룚�꾡에��뭽��`-m`餓롥뫝餓ㅸ죱訝�렩�뽫쉪岳→겘�싧만熬ョ뵪鵝쒏쑋岳�뵻�꾣젃嶺얌에����  瓦쇾릉�됮」��빳溫⒳퐷瓦쎽�閭η폋渦묇퍗瓦쇾틳�ζ틦�룟룚�꾡에����"
 
 #. type: Plain text
 #: en/git-tag.txt:189
 #, priority:240
 msgid "This option sets how the tag message is cleaned up.  The '<mode>' can be one of 'verbatim', 'whitespace' and 'strip'.  The 'strip' mode is default. The 'verbatim' mode does not change message at all, 'whitespace' removes just leading/trailing whitespace lines and 'strip' removes both whitespace and commentary."
-msgstr ""
+msgstr "瓦쇾릉�됮」溫양쉰雅녷젃嶺얌에��쉪歷끿릤�밧폀��  '<與▼폀>'��빳��'verbatim'竊덆�먨춻溫겼퐬竊됥��'whitespace'竊덄㈉�쏙펹��'strip'竊덂돟獵삼펹訝�쉪訝�訝ゃ��  �뜸릎竊�'strip'與▼폀��퍡溫ㅷ쉪��'verbatim'與▼폀若뚦뀲訝띷뵻�섆에��펽'whitespace'�ゅ닠�ㅵ뎺野�/�롥��꾤㈉�썼죱竊�'strip'�뚧뿶�좈솮令븀쇋�뚧낏�듽��"
 
 #. type: Plain text
 #: en/git-tag.txt:196
 #, priority:240
 msgid "Create a reflog for the tag. To globally enable reflogs for tags, see `core.logAllRefUpdates` in linkgit:git-config[1].  The negated form `--no-create-reflog` only overrides an earlier `--create-reflog`, but currently does not negate the setting of `core.logAllRefUpdates`."
-msgstr ""
+msgstr "訝뷸젃嶺얍닗兩뷰�訝ゅ폊�ⓩ뿥恙쀣�귟쫨�ⓨ��㎩쑑��뵪�뉒��꾢폊�ⓩ뿥恙쀯펽瑥룟뢿鰲� linkgit:git-config[1] 訝�쉪 `core.logAllRefUpdates`��  ��츣壤℡폀�� `--no-create-reflog` 鴉싪쫮�뽩뀍�띸쉪 `--create-reflog` 竊뚥퐜��뎺訝띴폏��츣 `core.logAllRefUpdates` �꾥�營���"
 
 #. type: Plain text
 #: en/git-tag.txt:202
 #, priority:240
 msgid "A string that interpolates `%(fieldname)` from a tag ref being shown and the object it points at.  The format is the same as that of linkgit:git-for-each-ref[1].  When unspecified, defaults to `%(refname:strip=2)`."
-msgstr ""
+msgstr "訝�訝ゅ춻寧╊림竊뚥퍗閭ｅ쑉�양ㅊ�꾣젃嶺얍폊�ⓨ뭽若껅��뉐릲�꾢�穩▽릎�믣��`%(fieldname)'��  �뜻졏凉뤶툗linkgit:git-for-each-ref[1]�멨릪��  壤볠쑋�뉐츣�띰펽容섋�訝�`%(refname:strip=2)`��"
 
 #. type: Labeled list
 #: en/git-tag.txt:203
@@ -56522,7 +56522,7 @@ msgstr "<tagname>"
 #: en/git-tag.txt:208
 #, priority:240
 msgid "The name of the tag to create, delete, or describe.  The new tag name must pass all checks defined by linkgit:git-check-ref-format[1].  Some of these checks may restrict the characters allowed in a tag name."
-msgstr ""
+msgstr "誤곩닗兩뷩�곩닠�ㅶ닑�뤺염�꾣젃嶺양쉪�띸㎞��  �경젃嶺얍릫恙낂』�싪퓝 linkgit:git-check-ref-format[1] 若싦퉱�꾣��됪��γ��  �뜸릎訝�雅쎿��ε룾�썽솏�뜸틙�뉒��띸㎞訝�뀅溫며쉪耶쀧Е��"
 
 #. type: Labeled list
 #: en/git-tag.txt:209 en/git.txt:394
@@ -56534,13 +56534,13 @@ msgstr "<commit>"
 #: en/git-tag.txt:213
 #, priority:240
 msgid "The object that the new tag will refer to, usually a commit.  Defaults to HEAD."
-msgstr ""
+msgstr "�경젃嶺얍컛凉뺟뵪�꾢�穩∽펽�싧만���訝ゆ룓雅ㅳ��  容섋�訝뷴퐪�띶늽����"
 
 #. type: Plain text
 #: en/git-tag.txt:220
 #, priority:240
 msgid "By default, 'git tag' in sign-with-default mode (-s) will use your committer identity (of the form `Your Name <your@email.address>`) to find a key.  If you want to use a different default key, you can specify it in the repository configuration as follows:"
-msgstr ""
+msgstr "容섋��끻넻訝뗰펽sign-with-default與▼폀訝뗧쉪'git tag'竊�-s竊됦폏鵝욜뵪鵝좂쉪�먧벡�낁벴餓쏙펷壤℡폀訝�`鵝좂쉪�띶춻<your@email.address>`竊됪씎野삥돻訝�訝ゅ칳�γ��  倻귝옖鵝졿꺍鵝욜뵪訝�訝や툖�뚨쉪容섋�野녽뮙竊뚥퐷��빳�ⓧ퍜佯볣뀓營�릎�뉐츣若껓펽倻귚툔竊�"
 
 #. type: delimited block -
 #: en/git-tag.txt:224
@@ -56556,55 +56556,55 @@ msgstr ""
 #: en/git-tag.txt:229
 #, priority:240
 msgid "`pager.tag` is only respected when listing tags, i.e., when `-l` is used or implied. The default is to use a pager.  See linkgit:git-config[1]."
-msgstr ""
+msgstr "`pager.tag`�ゅ쑉�쀥눣�뉒��띈˙弱딃뇥竊뚦뜵鵝욜뵪�뽪슅鹽뷰슴��`-l`�뜰�귡퍡溫ㅶ삸鵝욜뵪�녽〉�ⓦ��  �귟쭅 linkgit:git-config[1]��"
 
 #. type: Title ~
 #: en/git-tag.txt:234
 #, no-wrap, priority:240
 msgid "On Re-tagging"
-msgstr ""
+msgstr "�념틢�띷뼭�볠젃嶺�"
 
 #. type: Plain text
 #: en/git-tag.txt:238
 #, priority:240
 msgid "What should you do when you tag a wrong commit and you would want to re-tag?"
-msgstr ""
+msgstr "壤볞퐷�뉓�雅녵�訝ら뵗瑥�쉪�먧벡竊뚩�뚥퐷�녜뇥�경젃溫경뿶竊뚥퐷佯붻��롣퉰�싷폕"
 
 #. type: Plain text
 #: en/git-tag.txt:241
 #, priority:240
 msgid "If you never pushed anything out, just re-tag it. Use \"-f\" to replace the old one. And you're done."
-msgstr ""
+msgstr "倻귝옖鵝졽퍗�ゆ렓�곩댆�뜸퍟�경뼶竊뚦룵���띷뼭�뉓��귚슴��\"-f \"�ζ쎘�€뿧�꾣젃嶺얇�귞꽫�롣퐷弱긷츑�먧틙��"
 
 #. type: Plain text
 #: en/git-tag.txt:245
 #, priority:240
 msgid "But if you have pushed things out (or others could just read your repository directly), then others will have already seen the old tag. In that case you can do one of two things:"
-msgstr ""
+msgstr "鵝녶쫩�쒍퐷藥꿰퍘�③�곦틙竊덃닑�끻닽雅뷴룾餓η쎍�θ��뽨퐷�꾤뎵�у틩竊됵펽�ｄ퉰�ヤ볶弱긷럴瀯뤹쐦�겻틙�㎪젃嶺얇�귛쑉瓦숂쭕�끻넻訝뗰펽鵝졾룾餓ε쑉餓δ툔訝ㅷ쭕�싨퀡餓삯�됧끀訝�竊�"
 
 #. type: Plain text
 #: en/git-tag.txt:252
 #, priority:240
 msgid "The sane thing.  Just admit you screwed up, and use a different name. Others have already seen one tag-name, and if you keep the same name, you may be in the situation that two people both have \"version X\", but they actually have 'different' \"X\"'s.  So just call it \"X.1\" and be done with it."
-msgstr ""
+msgstr "�녷쇇�꾢걳力뺞삸��  �よ쫨�욤�鵝졿맄�멧틙竊뚦뭉鵝욜뵪訝�訝や툖�뚨쉪�띶춻�귛끀餓뽨볶藥꿰퍘�뗥댆雅녵�訝ゆ젃嶺얍릫燁곤펽倻귝옖鵝졽퓷�곭쎑�뚨쉪�띸㎞竊뚥퐷��꺗鴉싧눣�계퓳�루쉪�끻넻竊싦륵訝や볶�썸쐣 \"X��\"竊뚥퐜餓뽨뺄若욇솀訝딀쐣 \"訝띶릪 \"�� \"X\"��  ��餓ο펽�よ쫨�ュ츆 \"X.1 \"弱긷룾餓δ틙��"
 
 #. type: Plain text
 #: en/git-tag.txt:257
 #, priority:240
 msgid "The insane thing.  You really want to call the new version \"X\" too, 'even though' others have already seen the old one. So just use 'git tag -f' again, as if you hadn't already published the old one."
-msgstr ""
+msgstr "��땬�꾢걳力뺛��  鵝좂쐿�꾣꺍�딀뼭�덃쑍阿잏㎞訝� \"X\"竊뚢뙄弱썹��됧닽雅뷴럴瀯뤹쐦�겻틙�㎫뎵�с�귝�餓ε갚�띸뵪'git tag -f'竊뚦갚也썲깗鵝좄퓲亦→쐣�묈툋瓦뉑뿧�덃쑍訝��룔��"
 
 #. type: Plain text
 #: en/git-tag.txt:262
 #, priority:240
 msgid "However, Git does *not* (and it should not) change tags behind users back. So if somebody already got the old tag, doing a 'git pull' on your tree shouldn't just make them overwrite the old one."
-msgstr ""
+msgstr "�띈�뚳펽Git*訝띴폏*竊덁튋訝띶틪瑥ο펹�뚨��ⓩ댎�밧룜�뉒��귝�餓ε쫩�쒏쐣雅뷴럴瀯뤷풓�겻틙�㎫쉪�뉒�竊뚦쑉鵝좂쉪�묇툓�� \"git pull \"訝띶틪瑥θ�餓뽨뺄誤녺썣�㎫쉪�뉒���"
 
 #. type: Plain text
 #: en/git-tag.txt:269
 #, priority:240
 msgid "If somebody got a release tag from you, you cannot just change the tag for them by updating your own one. This is a big security issue, in that people MUST be able to trust their tag-names.  If you really want to do the insane thing, you need to just fess up to it, and tell people that you messed up. You can do that by making a very public announcement saying:"
-msgstr ""
+msgstr "倻귝옖�됦볶餓롣퐷�ｉ뇤孃쀥댆訝�訝ゅ룕躍껅젃嶺억펽鵝졽툖�썽�싪퓝�닸뼭鵝좄눎藥긺쉪�뉒��δ맏餓뽨뺄�밧룜�뉒��귟퓳���訝ゅ푽鸚㎫쉪若됧뀲��쥦竊뚦썱訝뷰볶餓у퓚窈삭꺗鸚잋에餓삡퍟餓х쉪�뉒��띲��  倻귝옖鵝좂쐿�꾣꺍�싦�餓띄뼬�귞쉪雅뗦깄竊뚥퐷��誤곫돽溫ㅸ퓳訝��뱄펽亮뜹몜瑥됦볶餓т퐷�욅졇雅녴�귚퐷��빳�싪퓝�묈툋訝�訝ら씆躍멨뀶凉��꾢뀶�딀씎�싧댆瓦쇾��뱄펽驪붷쫩瑥댐폏"
 
 #. type: delimited block -
 #: en/git-tag.txt:273
@@ -56612,7 +56612,7 @@ msgstr ""
 msgid ""
 "Ok, I messed up, and I pushed out an earlier version tagged as X. I\n"
 "then fixed something, and retagged the *fixed* tree as X again.\n"
-msgstr ""
+msgstr "也썲맕竊뚧닊�욅졇雅놅펽�묉렓�곦틙訝�訝ゆ젃溫겻맏X�꾣뿩�잏뎵�с��\n�뜹릮岳�쨳雅녵�雅쎽툥蜈울펽�덃뒍瓦쇾릉*岳�쨳��*��퐬�묌뇥�경젃溫겻맏X��\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:276
@@ -56620,7 +56620,7 @@ msgstr ""
 msgid ""
 "If you got the wrong tag, and want the new one, please delete\n"
 "the old one and fetch the new one by doing:\n"
-msgstr ""
+msgstr "倻귝옖鵝졾풓�겻틙�숃��꾣젃嶺억펽亮뜹툕�쎾풓�경뼭�꾣젃嶺억펽\n瑥룟닠�ㅶ뿧�꾣젃嶺억펽亮띌�싪퓝餓δ툔�밧폀�룟룚�곁쉪�뉒�竊�\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:279
@@ -56628,19 +56628,19 @@ msgstr ""
 msgid ""
 "\tgit tag -d X\n"
 "\tgit fetch origin tag X\n"
-msgstr ""
+msgstr "\tgit tag -d X\n\tgit fetch origin tag X\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:281
 #, no-wrap, priority:240
 msgid "to get my updated tag.\n"
-msgstr ""
+msgstr "餓θ렩孃쀦닊�꾣��경젃嶺얇��\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:283
 #, no-wrap, priority:240
 msgid "You can test which tag you have by doing\n"
-msgstr ""
+msgstr "鵝졾룾餓ι�싪퓝餓δ툔�밧폀役뗨캊鵝좂쉪�뉒�\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:285
@@ -56652,7 +56652,7 @@ msgstr "\tgit rev-parse X\n"
 #: en/git-tag.txt:287
 #, no-wrap, priority:240
 msgid "which should return 0123456789abcdef.. if you have the new version.\n"
-msgstr ""
+msgstr "倻귝옖鵝졿쐣�곁쉪�덃쑍竊뚦틪瑥θ퓭��0123456789abcdef��\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:289
@@ -56664,37 +56664,37 @@ msgstr "野밥틢�길�躍�씎�꾡툖堊�,�묇뺄曆길꽏�길춬��\n"
 #: en/git-tag.txt:294
 #, priority:240
 msgid "Does this seem a bit complicated? It *should* be. There is no way that it would be correct to just \"fix\" it automatically.  People need to know that their tags might have been changed."
-msgstr ""
+msgstr "瓦숂쐦壅룡씎��툖��쐣�밧쨳�귨폕若�*佯붻�*��퓳�루쉪�귟눎�� \"岳�쨳 \"若껅삸訝띶룾�썹쉪��  雅뷰뺄��誤곭윥�볞퍟餓х쉪�뉒���꺗藥꿰퍘熬ユ뵻�섅��"
 
 #. type: Title ~
 #: en/git-tag.txt:297
 #, no-wrap, priority:240
 msgid "On Automatic following"
-msgstr ""
+msgstr "�ⓧ툔�쀦깄�듕툔�ゅ뒯瓦쏂죱"
 
 #. type: Plain text
 #: en/git-tag.txt:302
 #, priority:240
 msgid "If you are following somebody else's tree, you are most likely using remote-tracking branches (eg. `refs/remotes/origin/master`).  You usually want the tags from the other end."
-msgstr ""
+msgstr "倻귝옖鵝졾쑉瓮잒릉�ヤ볶�꾣젒��퐬竊뚥퐷孃덂룾�썲쑉鵝욜뵪瓦쒐쮮瓮잒릉�꾢늽��펷堊뗥쫩竊�`refs/remotes/origin/master`竊됥��  鵝좈�싧만躍뚧쐹孃쀥댆�╊�塋�쉪�뉒���"
 
 #. type: Plain text
 #: en/git-tag.txt:309
 #, priority:240
 msgid "On the other hand, if you are fetching because you would want a one-shot merge from somebody else, you typically do not want to get tags from there.  This happens more often for people near the toplevel but not limited to them.  Mere mortals when pulling from each other do not necessarily want to automatically get private anchor point tags from the other person."
-msgstr ""
+msgstr "�╊��백씊竊뚦쫩�쒍퐷��썱訝뷸꺍餓롥닽雅븅궍�뚩렩孃쀤�轝→�㎩릦亮띈�뚦룚�꾬펽鵝좈�싧만訝띶툕�쎽퍗�ｉ뇤�룟풓�뉒���  瓦숂쭕�끻넻�당퍘躍멨룕�잌쑉�θ퓩遙섇콆�꾡볶翁ヤ툓竊뚥퐜訝띺솏雅롣퍟餓с��  ���싦볶餓롥��백궍�뚦룚訝쒑��띰펽訝띴�若싨꺍餓롥��백궍�뚩눎�②렩孃쀧쭅雅븅뵚�방젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:314
 #, priority:240
 msgid "Often, \"please pull\" messages on the mailing list just provide two pieces of information: a repo URL and a branch name; this is designed to be easily cut&pasted at the end of a 'git fetch' command line:"
-msgstr ""
+msgstr "�싧만竊뚪궙餓뜹닓烏ⓧ툓�� \"瑥룡땳\"岳→겘�ゆ룓堊쎽틙訝ㅶ씉岳→겘竊싦�訝� 餓볟틩URL �뚥�訝ゅ늽��릫燁곤폑瓦숃˙溫얕��먨룾餓θ슥�얍쑑�ゅ늾�뚨쿂兀닷쑉 \"git fetch \"�썰빱烏뚨쉪�ュ갼竊�"
 
 #. type: delimited block -
 #: en/git-tag.txt:317
 #, no-wrap, priority:240
 msgid "Linus, please pull from\n"
-msgstr ""
+msgstr "Linus竊뚩�餓롨퓳�뚧땳��\n"
 
 #. type: delimited block -
 #: en/git-tag.txt:319
@@ -56706,13 +56706,13 @@ msgstr "\tgit://git..../proj.git master\n"
 #: en/git-tag.txt:321
 #, ignore-ellipsis, no-wrap, priority:240
 msgid "to get the following updates...\n"
-msgstr ""
+msgstr "餓θ렩孃쀤빳訝뗦쎍��...\n"
 
 #. type: Plain text
 #: en/git-tag.txt:324
 #, priority:240
 msgid "becomes:"
-msgstr ""
+msgstr "�먧맏竊�"
 
 #. type: delimited block -
 #: en/git-tag.txt:327
@@ -56724,43 +56724,43 @@ msgstr "$ git pull git://git..../proj.git master\n"
 #: en/git-tag.txt:331
 #, priority:240
 msgid "In such a case, you do not want to automatically follow the other person's tags."
-msgstr ""
+msgstr "�②퓳燁띷깄�듕툔竊뚥퐷訝띶툕�쏂눎�②퇎�뤷��밭쉪�뉒���"
 
 #. type: Plain text
 #: en/git-tag.txt:339
 #, priority:240
 msgid "One important aspect of Git is its distributed nature, which largely means there is no inherent \"upstream\" or \"downstream\" in the system.  On the face of it, the above example might seem to indicate that the tag namespace is owned by the upper echelon of people and that tags only flow downwards, but that is not the case.  It only shows that the usage pattern determines who are interested in whose tags."
-msgstr ""
+msgstr "Git �꾡�訝ら뇥誤곫뼶�€삸若껆쉪�녶툋凉뤸�㎬뇽竊뚩퓳孃덂ㄷ葉뗥벧訝딀꼷�녕�楹사퍨訝�깹�됧쎓�됬쉪 \"訝딀만 \"�� \"訝뗦만\"��  餓롨〃�㏘툓�뗰펽訝딃씊�꾡풃耶먧세阿롨〃�롦젃嶺얍뫝�띸㈉�닸삸�긴툓掠귚볶鶯ユ떏�됬쉪竊뚩�뚧젃嶺얍룵�썲릲訝뗦탛�⑨펽鵝녵틟若욃뭉�욃쫩閭ㅳ��  若껃룵��〃�롳펽鵝욜뵪與▼폀�녑츣雅녻컖野배컖�꾣젃嶺얏꽏�닺땃��"
 
 #. type: Plain text
 #: en/git-tag.txt:351
 #, priority:240
 msgid "A one-shot pull is a sign that a commit history is now crossing the boundary between one circle of people (e.g. \"people who are primarily interested in the networking part of the kernel\") who may have their own set of tags (e.g. \"this is the third release candidate from the networking group to be proposed for general consumption with 2.6.21 release\") to another circle of people (e.g. \"people who integrate various subsystem improvements\").  The latter are usually not interested in the detailed tags used internally in the former group (that is what \"internal\" means).  That is why it is desirable not to follow tags automatically in this case."
-msgstr ""
+msgstr "訝�轝→�㎪땳�뽪삸訝�訝ゆ젃恙쀯펽烏ⓩ삇訝�訝ゆ룓雅ㅵ럣�꿩��②랬擁듾�訝ゅ쐢耶먲펷堊뗥쫩 \"訝삭쫨野밧냵�며쉪營묊퍥�ⓨ늽�잌뀾擁ｇ쉪雅�\"竊됧뭽�╊�訝ゅ쐢耶먲펷堊뗥쫩 \"�닷릦�꾤쭕耶먪내瀯잍뵻瓦쏁쉪雅�\"竊됦퉳�당쉪�뚪솏竊뚦릮�끻룾�썸쐣�ゅ런�꾡�也쀦젃嶺억펷堊뗥쫩 \"瓦숁삸營묊퍥瀯꾤쉪寧т툒訝ゅ�숅�됬뎵�э펽弱녶쑉2.6.21�덃쑍訝�˙兩븃��ⓧ틢訝��ф텋兀�\"竊됥��  �롨�낂�싧만野밧뎺訝�瀯꾢냵�ⓧ슴�①쉪瑥�퍏�뉒�訝띷꽏�닺땃竊덅퓳弱길삸 \"�낂깿 \"�꾣꼷�앾펹��  瓦쇿갚��맏餓�阿덂쑉瓦숂쭕�끻넻訝뗦�也썰툖誤곮눎�②퇎�뤸젃嶺얇��"
 
 #. type: Plain text
 #: en/git-tag.txt:357
 #, priority:240
 msgid "It may well be that among networking people, they may want to exchange the tags internal to their group, but in that workflow they are most likely tracking each other's progress by having remote-tracking branches.  Again, the heuristic to automatically follow such tags is a good thing."
-msgstr ""
+msgstr "�②퓳訝ょ퐨瀯쒐윥藥욑펽餓뽨뺄��꺗�념벡�㏘퍟餓у컦瀯꾢냵�①쉪�뉒�竊뚥퐜�③궍訝ゅ램鵝쒏탛葉뗤릎竊뚥퍟餓у푽��꺗���싪퓝�됭퓶葉뗨퇎甕ょ쉪�녷뵱�θ퇎甕ゅ��밭쉪瓦쎾콝��  �뚧졆竊뚩눎�②퇎甕よ퓳燁띷젃嶺양쉪��룕凉뤸뼶力뺜튋���訝ゅ�訝쒑���"
 
 #. type: Title ~
 #: en/git-tag.txt:360
-#, no-wrap, priority:240
+#, fuzzy, no-wrap, priority:240
 msgid "On Backdating Tags"
-msgstr ""
+msgstr "�념틢�욄변�뉒�"
 
 #. type: Plain text
 #: en/git-tag.txt:367
 #, priority:240
 msgid "If you have imported some changes from another VCS and would like to add tags for major releases of your work, it is useful to be able to specify the date to embed inside of the tag object; such data in the tag object affects, for example, the ordering of tags in the gitweb interface."
-msgstr ""
+msgstr "倻귝옖鵝졽퍗�╊�訝챉CS野쇔뀯雅녵�雅쎽엶�뱄펽亮뜻꺍訝뷰퐷藥δ퐳�꾡말誤곭뎵�ф렌�졿젃嶺억펽�썲쩅�뉐츣葯뚦뀯�뉒�野배괌�낂깿�꾣뿥�잍삸孃덃쐣�①쉪竊쎿젃嶺얍�穩▽릎�꾥퓳燁띷빊��폏雅㎫뵟壤긷뱧竊뚥풃倻귨펽gitweb�뚪씊訝�젃嶺양쉪�믣틣��"
 
 #. type: Plain text
 #: en/git-tag.txt:371
 #, priority:240
 msgid "To set the date used in future tag objects, set the environment variable GIT_COMMITTER_DATE (see the later discussion of possible values; the most common form is \"YYYY-MM-DD HH:MM\")."
-msgstr ""
+msgstr "誤곮�營�쑋�ζ젃嶺얍�穩▽릎鵝욜뵪�꾣뿥�잞펽瑥룩�營�렞罌껃룜�뢋IT_COMMITTER_DATE竊덅쭅�롩씊�념틢��꺗�겼�쇘쉪溫②�竊쎿�躍멱쭅�꾢숱凉뤸삸 \"YYY-MM-DD HH:MM\"竊됥��"
 
 #. type: delimited block -
 #: en/git-tag.txt:376
@@ -56772,7 +56772,7 @@ msgstr "$ GIT_COMMITTER_DATE=\"2006-10-02 10:31\" git tag -s v1.0.1\n"
 #: en/git-tag.txt:389
 #, priority:240
 msgid "linkgit:git-check-ref-format[1].  linkgit:git-config[1]."
-msgstr ""
+msgstr "linkgit:git-check-ref-format[1].  linkgit:git-config[1]."
 
 #. type: Title =
 #: en/git.txt:2
@@ -60774,7 +60774,7 @@ msgstr "git-worktree(1)"
 #: en/git-worktree.txt:7
 #, priority:240
 msgid "git-worktree - Manage multiple working trees"
-msgstr ""
+msgstr "git-worktree - 嶸←릤鸚싦릉藥δ퐳��"
 
 #. type: Plain text
 #: en/git-worktree.txt:21
@@ -60789,61 +60789,61 @@ msgid ""
 "'git worktree remove' [-f] <worktree>\n"
 "'git worktree repair' [<path>...]\n"
 "'git worktree unlock' <worktree>\n"
-msgstr ""
+msgstr "'git worktree add' [-f] [--detach] [--checkout] [--lock [--reason <耶쀧Е訝�>]]\n\t\t   [-b <�겼늽��>] <瓮�푶> [<�먧벡��>]\n'git worktree list' [-v | --porcelain [-z]]\n'git worktree lock' [--reason <耶쀧Е訝�>] <藥δ퐳��>\n'git worktree move' <藥δ퐳��> <�겼늽��>\n'git worktree prune' [-n] [-v] [--expire <�경쐿>]\n'git worktree remove' [-f] <藥δ퐳��>\n'git worktree repair' [<瓮�푶>...]\n'git worktree unlock' <藥δ퐳��>\n"
 
 #. type: Plain text
 #: en/git-worktree.txt:26
 #, priority:240
 msgid "Manage multiple working trees attached to the same repository."
-msgstr ""
+msgstr "嶸←릤�꾢콪雅롥릪訝�餓볟틩�꾢쩀訝ゅ램鵝쒎뙷��"
 
 #. type: Plain text
 #: en/git-worktree.txt:32
 #, priority:240
 msgid "A git repository can support multiple working trees, allowing you to check out more than one branch at a time.  With `git worktree add` a new working tree is associated with the repository, along with additional metadata that differentiates that working tree from others in the same repository.  The working tree, along with this metadata, is called a \"worktree\"."
-msgstr ""
+msgstr "訝�訝� git 餓볟틩��빳��똻鸚싦릉藥δ퐳�븝펽�곮�鵝졽�轝←��뷴쩀訝ゅ늽����  �싪퓝`git worktree add`竊뚥�訝ゆ뼭�꾢램鵝쒎뙷訝롣퍜佯볡쎑�녘걫竊뚦릪�띈퓲�됮쥫鸚뽫쉪�껅빊��펽餓ε뙷�녻�藥δ퐳�뷰툗�뚥�餓볟틩訝�쉪�뜸퍟藥δ퐳�뷩��  藥δ퐳�븀쎅壤뺞젒竊뚩퓹�뚩퓳雅쎾뀇�경뜮竊뚩˙燁겻맏 \"藥δ퐳��\"��"
 
 #. type: Plain text
 #: en/git-worktree.txt:38
 #, priority:240
 msgid "This new worktree is called a \"linked worktree\" as opposed to the \"main worktree\" prepared by linkgit:git-init[1] or linkgit:git-clone[1].  A repository has one main worktree (if it's not a bare repository) and zero or more linked worktrees. When you are done with a linked worktree, remove it with `git worktree remove`."
-msgstr ""
+msgstr "瓦쇾릉�곁쉪藥δ퐳�븃˙燁겻맏 \"�얏렏藥δ퐳��\"竊뚥툗 linkgit:git-init[1] �� linkgit:git-clone[1] ���녶쨭�� \"訝삣램鵝쒎뙷 \"�멨�佯붵��  訝�訝や퍜佯볠쐣訝�訝や말藥δ퐳�븝펷倻귝옖若껂툖���訝よ８餓볟틩竊됧뭽�뜸릉�뽩쩀訝ら벦�ε램鵝쒎뙷�귛퐪鵝좂뵪若뚥�訝ら벦�ε램鵝쒎뙷�롳펽�� `git worktree remove` �좈솮若껁��"
 
 #. type: Plain text
 #: en/git-worktree.txt:50
 #, priority:240
 msgid "In its simplest form, `git worktree add <path>` automatically creates a new branch whose name is the final component of `<path>`, which is convenient if you plan to work on a new topic. For instance, `git worktree add ../hotfix` creates new branch `hotfix` and checks it out at path `../hotfix`. To instead work on an existing branch in a new worktree, use `git worktree add <path> <branch>`. On the other hand, if you just plan to make some experimental changes or do testing without disturbing existing development, it is often convenient to create a 'throwaway' worktree not associated with any branch. For instance, `git worktree add -d <path>` creates a new worktree with a detached `HEAD` at the same commit as the current branch."
-msgstr ""
+msgstr "�ⓨ끀��嶸��뺟쉪壤℡폀訝�펽`git worktree add <瓮�푶>`�ゅ뒯�쎾뻠訝�訝ゆ뼭�꾢늽��펽�뜹릫燁경삸`<瓮�푶>`�꾣��롣�訝ょ퍍�먬깿�놅펽倻귝옖鵝좄��믣쑉訝�訝ゆ뼭�꾡말窯섆툓藥δ퐳竊뚩퓳孃덃뼶堊욍�귚풃倻귨펽`git worktree add .../hotfix`�쎾뻠雅녷뼭�꾢늽��`hotfix`竊뚦뭉�②러孃�`.../hotfix`鸚꾤��뷴츆�귛쫩�쒑쫨�ⓧ�訝ゆ뼭�꾢램鵝쒎뙷訝�쨪�녺렟�됬쉪�녷뵱竊뚦룾餓δ슴��`git worktree add <瓮�푶> <�녷뵱>`�귛룱訝��백씊竊뚦쫩�쒍퐷�ゆ삸�볡츞�싦�雅쎾츩謠뚧�㎫쉪岳�뵻竊뚧닑�끻쑉訝띶쉽�띸렟�됧��묊쉪�끻넻訝뗨퓵烏뚧탩瑥뺧펽�쎾뻠訝�訝や툖訝롣뻣鵝뺝늽��쎑�녘걫�� \"�쎾펱凉� \"藥δ퐳�븅�싧만��푽�밥씩�꾠�귚풃倻귨펽`git worktree add -d <瓮�푶>`�ⓧ툗壤볟뎺�녷뵱�멨릪�꾣룓雅ㅴ릎竊뚦닗兩뷰�訝ゅ를�됧늽獵�`HEAD`�꾣뼭藥δ퐳�뷩��"
 
 #. type: Plain text
 #: en/git-worktree.txt:57
 #, priority:240
 msgid "If a working tree is deleted without using `git worktree remove`, then its associated administrative files, which reside in the repository (see \"DETAILS\" below), will eventually be removed automatically (see `gc.worktreePruneExpire` in linkgit:git-config[1]), or you can run `git worktree prune` in the main or any linked worktree to clean up any stale administrative files."
-msgstr ""
+msgstr "倻귝옖亦→쐣鵝욜뵪 `git worktree remove` 弱긷닠�ㅴ틙藥δ퐳�븝펽�ｄ퉰若껆쉪�멨뀽嶸←릤�뉏뻑竊뚦뜵要삥뎻�ⓧ퍜佯볞릎�꾣뻼餓띰펷鰲곦툔�®쉪 \"瑥�퍏瑥닸삇\"竊됵펽��瀯덁폏熬ヨ눎�ⓨ닠�ㅿ펷鰲� linkgit:git-config[1] 訝�쉪 `gc.worktreePruneExpire`竊됵펽�뽬�끺퐷��빳�ⓧ말藥δ퐳�뷸닑餓삡퐬�얏렏藥δ퐳�뷰릎瓦먫죱`git worktree prune` �ζ툍�녵뻣鵝뺠퓝�띄쉪嶸←릤�뉏뻑��"
 
 #. type: Plain text
 #: en/git-worktree.txt:63
 #, priority:240
 msgid "If the working tree for a linked worktree is stored on a portable device or network share which is not always mounted, you can prevent its administrative files from being pruned by issuing the `git worktree lock` command, optionally specifying `--reason` to explain why the worktree is locked."
-msgstr ""
+msgstr "倻귝옖訝�訝ら벦�η쉪藥δ퐳�뷴춼�ⓨ쑉堊욘맳溫얍쨭�뽫퐨瀯쒎뀻雅ヤ툓竊뚩�뚩퓳雅쏂�鸚뉐뭉訝띷�삥삸熬ユ똼饔쏙펽鵝졾룾餓ι�싪퓝�묈툋`git worktree lock`�썰빱�ι삻閭℡끀嶸←릤�뉏뻑熬ヤ엶�わ펽��빳鵝욜뵪�됮」`--reason`�θ㎗�듾맏餓�阿덂램鵝쒏젒熬ラ봺若싥��"
 
 #. type: Labeled list
 #: en/git-worktree.txt:66
 #, no-wrap, priority:240
 msgid "add <path> [<commit-ish>]"
-msgstr ""
+msgstr "add <瓮�푶> [<�먧벡��>]"
 
 #. type: Plain text
 #: en/git-worktree.txt:72
 #, priority:240
 msgid "Create a worktree at `<path>` and checkout `<commit-ish>` into it. The new worktree is linked to the current repository, sharing everything except per-worktree files such as `HEAD`, `index`, etc. As a convenience, `<commit-ish>` may be a bare \"`-`\", which is synonymous with `@{-1}`."
-msgstr ""
+msgstr "��`<瓮�푶>`�쎾뻠訝�訝ゅ램鵝쒏젒竊뚦뭉弱�`<�먧벡��>`嶺얍뀯�뜸릎�귝뼭�꾢램鵝쒎뙷熬ラ벦�ε댆壤볟뎺餓볟틩竊뚦뀻雅ラ솮驪뤶릉藥δ퐳�뷸뻼餓띰펷倻�`HEAD`��`index`嶺됵펹阿뗥쨼�꾡��뉎�귚맏雅녷뼶堊욤돈鰲곻펽`<�먧벡��>`��빳���訝ゅ뀎燁껆쭇��\"`-`\"竊뚦츆訝�`@{-1}`�뚥퉱��"
 
 #. type: Plain text
 #: en/git-worktree.txt:77
 #, priority:240
 msgid "If `<commit-ish>` is a branch name (call it `<branch>`) and is not found, and neither `-b` nor `-B` nor `--detach` are used, but there does exist a tracking branch in exactly one remote (call it `<remote>`)  with a matching name, treat as equivalent to:"
-msgstr ""
+msgstr "倻귝옖`<�먧벡��>`���訝ゅ늽��릫燁곤펷燁겼끀訝�`<�녷뵱>`竊됵펽亮뜸툝亦→쐣�얍댆竊뚥튋亦→쐣鵝욜뵪`-b`��`-B`��`-detach`竊뚥퐜簾�츩�ⓩ�也썰�訝よ퓶葉뗤퍜佯볩펷燁겼끀訝�`<瓦쒐쮮餓볟틩>`竊됦릎耶섇쑉訝�訝ゅ릫燁겼뙶�띸쉪瓮잒릉�녷뵱竊뚦닕鰲녵맏嶺됧릪雅롳폏"
 
 #. type: delimited block -
 #: en/git-worktree.txt:80
@@ -60855,19 +60855,19 @@ msgstr "$ git worktree add --track -b <branch> <path> <remote>/<branch>\n"
 #: en/git-worktree.txt:90
 #, priority:240
 msgid "If the branch exists in multiple remotes and one of them is named by the `checkout.defaultRemote` configuration variable, we'll use that one for the purposes of disambiguation, even if the `<branch>` isn't unique across all remotes. Set it to e.g. `checkout.defaultRemote=origin` to always checkout remote branches from there if `<branch>` is ambiguous but exists on the `origin` remote. See also `checkout.defaultRemote` in linkgit:git-config[1]."
-msgstr ""
+msgstr "倻귝옖瑥ε늽��춼�ⓧ틢鸚싦릉瓦쒐쮮餓볟틩竊뚦뭉訝붷끀訝��訝ゆ삸��`checkout.defaultRemote`�띸쉰�섌뇧�썲릫�꾬펽訝뷰틙易덆솮閭㏛퉱竊뚧닊餓у컛鵝욜뵪瑥ε룜�륅펽�념슴`<�녷뵱>`�ⓩ��됭퓶葉뗤릎亮뜸툖����귛컛�띈�營�맏堊뗥쫩 `checkout.defaultRemote=origin`竊뚥빳堊욕쑉`<�녷뵱>`訝띷삇簾�퐜耶섇쑉雅�'origin'瓦쒐쮮�띰펽�삥삸餓롩궍�뚨��븃퓶葉뗥늽���귛뢿鰲� linkgit:git-config[1] 訝�쉪 `checkout.defaultRemote`��"
 
 #. type: Plain text
 #: en/git-worktree.txt:98
 #, priority:240
 msgid "If `<commit-ish>` is omitted and neither `-b` nor `-B` nor `--detach` used, then, as a convenience, the new worktree is associated with a branch (call it `<branch>`) named after `$(basename <path>)`.  If `<branch>` doesn't exist, a new branch based on `HEAD` is automatically created as if `-b <branch>` was given.  If `<branch>` does exist, it will be checked out in the new worktree, if it's not checked out anywhere else, otherwise the command will refuse to create the worktree (unless `--force` is used)."
-msgstr ""
+msgstr "倻귝옖�곭븼雅�`<�먧벡��>`竊뚥튋亦→쐣鵝욜뵪`-b`��`-B`��`-detach`竊뚪궍阿덁퐳訝뷰�燁띷뼶堊울펽�곁쉪藥δ퐳�묈컛訝롣�訝や빳`$(basename <瓮�푶>)`�썲릫�꾢늽��펷燁겻맏`<�녷뵱>`竊됬쎑�녘걫��  倻귝옖`<�녷뵱>`訝띶춼�⑨펽訝�訝ゅ읃雅�`HEAD`�꾣뼭�녷뵱弱녻˙�ゅ뒯�쎾뻠竊뚦갚�뤹퍢��`-b <�녷뵱>`訝��룔��  倻귝옖`<�녷뵱>`簾�츩耶섇쑉竊뚦츆弱녶쑉�곁쉪藥δ퐳�묇릎熬ョ��븝펽倻귝옖若껅깹�됧쑉�뜸퍟�경뼶熬ョ��븝펽��닕�썰빱弱녷땼瀯앭닗兩뷴램鵝쒎뙷竊덆솮�욂슴��`--force`竊됥��"
 
 #. type: Plain text
 #: en/git-worktree.txt:107
 #, priority:240
 msgid "List details of each worktree.  The main worktree is listed first, followed by each of the linked worktrees.  The output details include whether the worktree is bare, the revision currently checked out, the branch currently checked out (or \"detached HEAD\" if none), \"locked\" if the worktree is locked, \"prunable\" if the worktree can be pruned by the `prune` command."
-msgstr ""
+msgstr "�쀥눣驪뤶릉藥δ퐳�븀쉪瀯녻뒄��  訝삣램鵝쒎뙷熬ラ쫿�덂닓�븝펽�η���캀訝ら벦�ε램鵝쒎뙷��  渦볟눣�꾤퍏�귛똿�ц�藥δ퐳�뷸삸�╊맏獒멩젒竊뚦퐪�띸��븀쉪岳���덌펽壤볟뎺汝��븀쉪�녷뵱竊덂쫩�쒏깹�됧닕訝� \"�녺┿�껰EAD\"竊됵펽倻귝옖藥δ퐳�묋˙�곩츣�쇾맏 \"�곩츣\"竊뚦쫩�쒎램鵝쒏젒��빳熬�`prune`�썰빱岳�돦�쇾맏 \"��엶��\"��"
 
 #. type: Labeled list
 #: en/git-worktree.txt:108
@@ -60879,7 +60879,7 @@ msgstr "lock"
 #: en/git-worktree.txt:114
 #, priority:240
 msgid "If a worktree is on a portable device or network share which is not always mounted, lock it to prevent its administrative files from being pruned automatically. This also prevents it from being moved or deleted.  Optionally, specify a reason for the lock with `--reason`."
-msgstr ""
+msgstr "倻귝옖訝�訝ゅ램鵝쒎뙷�ⓧ씩�뷴폀溫얍쨭�뽫퐨瀯쒎뀻雅ヤ툓竊뚩�뚩퓳訝よ�鸚뉑닑營묊퍥�긴벴亮뜸툖�삥삸熬ユ똼饔쏙펽瑥룬봺若싧츆餓ι삻閭℡끀嶸←릤�뉏뻑熬ヨ눎�ⓧ엶�ゃ�귟퓳阿잌룾餓ι삻閭℡츆熬ョ㎉�ⓩ닑�좈솮��  ��빳�됪떓��`--reason`�됮」�ζ뙁若싮봺若싩쉪�잌썱��"
 
 #. type: Labeled list
 #: en/git-worktree.txt:115
@@ -60891,49 +60891,49 @@ msgstr "move"
 #: en/git-worktree.txt:121
 #, priority:240
 msgid "Move a worktree to a new location. Note that the main worktree or linked worktrees containing submodules cannot be moved with this command. (The `git worktree repair` command, however, can reestablish the connection with linked worktrees if you move the main worktree manually.)"
-msgstr ""
+msgstr "弱녵�訝ゅ램鵝쒎뙷燁삣뒯�겻�訝ゆ뼭�꾡퐤營��귝낏�륅펽訝삣램鵝쒎뙷�뽩똿�ュ춴與▼쓼�꾦벦�ε램鵝쒎뙷訝띹꺗�ⓩ��썰빱燁삣뒯��(�띈�뚳펽倻귝옖鵝졿뎸�①㎉�ⓧ말藥δ퐳�븝펽`git worktree repair`�썰빱��빳�띷뼭兩븀쳦訝롩벦�ε램鵝쒎뙷�꾥퓹�γ�귨펹"
 
 #. type: Plain text
 #: en/git-worktree.txt:125
 #, priority:240
 msgid "Prune worktree information in `$GIT_DIR/worktrees`."
-msgstr ""
+msgstr "岳�돦`$GIT_DIR/worktrees`訝�쉪藥δ퐳�뷰에����"
 
 #. type: Plain text
 #: en/git-worktree.txt:132
 #, priority:240
 msgid "Remove a worktree. Only clean worktrees (no untracked files and no modification in tracked files) can be removed. Unclean worktrees or ones with submodules can be removed with `--force`. The main worktree cannot be removed."
-msgstr ""
+msgstr "燁삯솮訝�訝ゅ램鵝쒎뙷�귛룵�됧묾���꾢램鵝쒎뙷竊덃깹�됪쑋瓮잒릉�꾣뻼餓뜹뭽�や엶�밭쉪瓮잒릉�뉏뻑竊됧룾餓θ˙�좈솮�귟꼷藥δ퐳�뷸닑�됧춴與▼쓼�꾢램鵝쒎뙷��빳�� `--force` �좈솮�귚말藥δ퐳�뷰툖�썼˙�좈솮��"
 
 #. type: Labeled list
 #: en/git-worktree.txt:133
 #, ignore-ellipsis, no-wrap, priority:240
 msgid "repair [<path>...]"
-msgstr ""
+msgstr "repair [<瓮�푶>...]"
 
 #. type: Plain text
 #: en/git-worktree.txt:137
 #, priority:240
 msgid "Repair worktree administrative files, if possible, if they have become corrupted or outdated due to external factors."
-msgstr ""
+msgstr "倻귝옖��꺗�꾥캕竊뚥엶鸚띶램鵝쒎뙷�꾤��녷뻼餓띰펽倻귝옖若껂뺄�긴틢鸚뽭깿�좂킔�뚦룜孃쀦뜜�뤸닑瓦뉑뿶��"
 
 #. type: Plain text
 #: en/git-worktree.txt:142
 #, priority:240
 msgid "For instance, if the main worktree (or bare repository) is moved, linked worktrees will be unable to locate it. Running `repair` in the main worktree will reestablish the connection from linked worktrees back to the main worktree."
-msgstr ""
+msgstr "堊뗥쫩竊뚦쫩�쒍말藥δ퐳�븝펷�뽬８餓볟틩竊됭˙燁삣뒯竊뚪벦�ε램鵝쒎뙷弱녷뿞力뺞돻�겼츆�귛쑉訝삣램鵝쒎뙷訝�퓧烏� `repair` 弱녽뇥�겼뻠塋뗤퍗�얏렏藥δ퐳�뷴댆訝삣램鵝쒎뙷�꾥퓹�γ��"
 
 #. type: Plain text
 #: en/git-worktree.txt:149
 #, priority:240
 msgid "Similarly, if the working tree for a linked worktree is moved without using `git worktree move`, the main worktree (or bare repository) will be unable to locate it. Running `repair` within the recently-moved worktree will reestablish the connection. If multiple linked worktrees are moved, running `repair` from any worktree with each tree's new `<path>` as an argument, will reestablish the connection to all the specified paths."
-msgstr ""
+msgstr "�뚧졆�곤펽倻귝옖亦→쐣鵝욜뵪 `git worktree move` 弱긺㎉�ⓧ틙�얏렏藥δ퐳�븝펽訝삣램鵝쒎뙷竊덃닑獒멧퍜佯볩펹弱녷뿞力뺝츣鵝띶츆�귛쑉��瓦묊㎉�①쉪藥δ퐳�뷰릎瓦먫죱`repair`弱녽뇥�겼뻠塋뗨퓹�γ�귛쫩�쒎쩀訝ら벦�ε램鵝쒎뙷熬ョ㎉�⑨펽�ⓧ뻣鵝뺝램鵝쒎뙷訝�퓧烏�`repair`竊뚥빳驪뤶릉�묊쉪��`<瓮�푶>`鵝쒍맏�귝빊竊뚦컛�띷뼭兩븀쳦訝롦��됪뙁若싪러孃꾤쉪瓦욄렏��"
 
 #. type: Plain text
 #: en/git-worktree.txt:154
 #, priority:240
 msgid "If both the main worktree and linked worktrees have been moved manually, then running `repair` in the main worktree and specifying the new `<path>` of each linked worktree will reestablish all connections in both directions."
-msgstr ""
+msgstr "倻귝옖訝삣램鵝쒎뙷�뚪벦�ε램鵝쒎뙷�썼˙�뗥뒯燁삣뒯竊뚪궍阿덂쑉訝삣램鵝쒎뙷訝�퓧烏�`repair`亮뜻뙁若싨캀訝ら벦�ε램鵝쒏젒�꾣뼭`<瓮�푶>`弱녽뇥�겼뻠塋뗤륵訝ゆ뼶�묊쉪���됭퓹�γ��"
 
 #. type: Labeled list
 #: en/git-worktree.txt:155
@@ -60945,25 +60945,25 @@ msgstr "unlock"
 #: en/git-worktree.txt:158
 #, priority:240
 msgid "Unlock a worktree, allowing it to be pruned, moved or deleted."
-msgstr ""
+msgstr "鰲ｉ봺訝�訝ゅ램鵝쒎뙷竊뚦뀅溫멨츆熬ヤ엶�ゃ�곭㎉�ⓩ닑�좈솮��"
 
 #. type: Plain text
 #: en/git-worktree.txt:170
 #, priority:240
 msgid "By default, `add` refuses to create a new worktree when `<commit-ish>` is a branch name and is already checked out by another worktree, or if `<path>` is already assigned to some worktree but is missing (for instance, if `<path>` was deleted manually). This option overrides these safeguards. To add a missing but locked worktree path, specify `--force` twice."
-msgstr ""
+msgstr "容섋��끻넻訝뗰펽壤�`<�먧벡��>`���訝ゅ늽��릫燁곤펽亮뜸툝藥꿰퍘熬ュ룱訝�訝ゅ램鵝쒏젒嶺얍눣竊뚧닑��`<瓮�푶>`藥꿰퍘熬ュ늽�띸퍢�먧릉藥δ퐳�묕펽鵝녵륭鸚긴틙竊덁풃倻귨펽倻귝옖`<瓮�푶>`熬ユ뎸�ⓨ닠�ㅿ펹竊�`add`�믥퍦�쎾뻠訝�訝ゆ뼭�꾢램鵝쒏젒�귟퓳訝ら�됮」誤녺썣雅녻퓳雅쎽퓷�ㅶ렕�썬�귟쫨曆삣뒥訝�訝ょ성鸚긴퐜�곩츣�꾢램鵝쒎뙷瓮�푶竊뚩��뉐츣`--force`訝ㅶА��"
 
 #. type: Plain text
 #: en/git-worktree.txt:175
 #, priority:240
 msgid "`move` refuses to move a locked worktree unless `--force` is specified twice. If the destination is already assigned to some other worktree but is missing (for instance, if `<new-path>` was deleted manually), then `--force` allows the move to proceed; use `--force` twice if the destination is locked."
-msgstr ""
+msgstr "`move`�믥퍦燁삣뒯訝�訝よ˙�곩츣�꾢램鵝쒎뙷竊뚪솮��`--force`熬ユ뙁若싦륵轝▲�귛쫩�쒐쎅�꾢쑑藥꿰퍘熬ュ늽�띸퍢�뜸퍟藥δ퐳�븝펽鵝녷깹�됪돻�곤펷堊뗥쫩竊뚦쫩��`<�계러孃�>`熬ユ뎸�ⓨ닠�ㅿ펹竊뚪궍阿�`--force`�곮�燁삣뒯竊쎾쫩�쒐쎅�꾢쑑熬ラ봺若싷펽�쇾슴��`--force`訝ㅶА��"
 
 #. type: Plain text
 #: en/git-worktree.txt:178
 #, priority:240
 msgid "`remove` refuses to remove an unclean worktree unless `--force` is used.  To remove a locked worktree, specify `--force` twice."
-msgstr ""
+msgstr "`remove`�믥퍦�좈솮訝�訝よ꼷藥δ퐳�븝펽�ㅹ씆鵝욜뵪`--force`��  誤곩닠�ㅴ�訝ら봺若싩쉪藥δ퐳�븝펽��誤곫뙁若�`--force`訝ㅶА��"
 
 #. type: Plain text
 #: en/git-worktree.txt:187