Merge pull request #217 from oldsharp/prq-translate-refspec-original-pull-74

Translate 10-git-internals refspec (Originally #74 )

Author: networm

book/10-git-internals/sections/refspec.asc

@@ -1,15 +1,15 @@
 [[_refspec]]
-=== The Refspec
+=== 引用规格
 
-Throughout this book, we've used simple mappings from remote branches to local references, but they can be more complex.
-Suppose you add a remote like this:
+纵观全书，我们已经使用过一些诸如远程分支到本地引用的简单映射方式，但这种映射可以更复杂。
+假设你添加了这样一个远程版本库：
 
 [source,console]
 ----
 $ git remote add origin https://github.com/schacon/simplegit-progit
 ----
 
-It adds a section to your `.git/config` file, specifying the name of the remote (`origin`), the URL of the remote repository, and the refspec for fetching:
+上述命令会在你的 `.git/config` 文件中添加一个小节，并在其中指定远程版本库的名称（`origin`）、URL 和一个用于获取操作的引用规格（refspec）：
 
 [source,ini]
 ----
@@ -18,11 +18,11 @@ It adds a section to your `.git/config` file, specifying the name of the remote
 	fetch = +refs/heads/*:refs/remotes/origin/*
 ----
 
-The format of the refspec is an optional `+`, followed by `<src>:<dst>`, where `<src>` is the pattern for references on the remote side and `<dst>` is where those references will be written locally.
-The `+` tells Git to update the reference even if it isn't a fast-forward.
+引用规格的格式由一个可选的 `+` 号和紧随其后的 `<src>:<dst>` 组成，其中 `<src>` 是一个模式（pattern），代表远程版本库中的引用；`<dst>` 是那些远程引用在本地所对应的位置。
+`+` 号告诉 Git 即使在不能快进的情况下也要（强制）更新引用。
 
-In the default case that is automatically written by a `git remote add` command, Git fetches all the references under `refs/heads/` on the server and writes them to `refs/remotes/origin/` locally.
-So, if there is a `master` branch on the server, you can access the log of that branch locally via
+默认情况下，引用规格由 `git remote add` 命令自动生成， Git 获取服务器中 `refs/heads/` 下面的所有引用，并将它写入到本地的 `refs/remotes/origin/` 中。
+所以，如果服务器上有一个 `master` 分支，我们可以在本地通过下面这种方式来访问该分支上的提交记录：
 
 [source,console]
 ----
@@ -31,26 +31,26 @@ $ git log remotes/origin/master
 $ git log refs/remotes/origin/master
 ----
 
-They're all equivalent, because Git expands each of them to `refs/remotes/origin/master`.
+上面的三个命令作用相同，因为 Git 会把它们都扩展成 `refs/remotes/origin/master`。
 
-If you want Git instead to pull down only the `master` branch each time, and not every other branch on the remote server, you can change the fetch line to
+如果想让 Git 每次只拉取远程的 `master` 分支，而不是所有分支，可以把（引用规格的）获取那一行修改为：
 
 [source]
 ----
 fetch = +refs/heads/master:refs/remotes/origin/master
 ----
 
-This is just the default refspec for `git fetch` for that remote.
-If you want to do something one time, you can specify the refspec on the command line, too.
-To pull the `master` branch on the remote down to `origin/mymaster` locally, you can run
+这仅是针对该远程版本库的 `git fetch` 操作的默认引用规格。
+如果有某些只希望被执行一次的操作，我们也可以在命令行指定引用规格。
+若要将远程的 `master` 分支拉到本地的 `origin/mymaster` 分支，可以运行：
 
 [source,console]
 ----
 $ git fetch origin master:refs/remotes/origin/mymaster
 ----
 
-You can also specify multiple refspecs.
-On the command line, you can pull down several branches like so:
+你也可以指定多个引用规格。
+在命令行中，你可以按照如下的方式拉取多个分支：
 
 [source,console]
 ----
@@ -61,11 +61,11 @@ From [email protected]:schacon/simplegit
  * [new branch]      topic      -> origin/topic
 ----
 
-In this case, the  master branch pull was rejected because it wasn't a fast-forward reference.
-You can override that by specifying the `+` in front of the refspec.
+在这个例子中，对 `master` 分支的拉取操作被拒绝，因为它不是一个可以快进的引用。
+我们可以通过在引用规格之前指定 `+` 号来覆盖该规则。
 
-You can also specify multiple refspecs for fetching in your configuration file.
-If you want to always fetch the master and experiment branches, add two lines:
+你也可以在配置文件中指定多个用于获取操作的引用规格。
+如果想在每次获取时都包括 `master` 和 `experiment` 分支，添加如下两行：
 
 [source,ini]
 ----
@@ -75,15 +75,15 @@ If you want to always fetch the master and experiment branches, add two lines:
 	fetch = +refs/heads/experiment:refs/remotes/origin/experiment
 ----
 
-You can't use partial globs in the pattern, so this would be invalid:
+我们不能在模式中使用部分通配符，所以像下面这样的引用规格是不合法的：
 
 [source]
 ----
 fetch = +refs/heads/qa*:refs/remotes/origin/qa*
 ----
 
-However, you can use namespaces (or directories) to accomplish something like that.
-If you have a QA team that pushes a series of branches, and you want to get the master branch and any of the QA team's branches but nothing else, you can use a config section like this:
+但我们可以使用命名空间（或目录）来达到类似目的。
+假设你有一个 QA 团队，他们推送了一系列分支，同时你只想要获取 `master` 和 QA 团队的所有分支而不关心其他任何分支，那么可以使用如下配置：
 
 [source,ini]
 ----
@@ -93,22 +93,22 @@ If you have a QA team that pushes a series of branches, and you want to get the
 	fetch = +refs/heads/qa/*:refs/remotes/origin/qa/*
 ----
 
-If you have a complex workflow process that has a QA team pushing branches, developers pushing branches, and integration teams pushing and collaborating on remote branches, you can namespace them easily this way.
+如果项目的工作流很复杂，有 QA 团队推送分支、开发人员推送分支、集成团队推送并且在远程分支上展开协作，你就可以像这样（在本地）为这些分支创建各自的命名空间，非常方便。
 
 [[_pushing_refspecs]]
-==== Pushing Refspecs
+==== 引用规格推送
 
-It's nice that you can fetch namespaced references that way, but how does the QA team get their branches into a `qa/` namespace in the first place?
-You accomplish that by using refspecs to push.
+像上面这样从远程版本库获取已在命名空间中的引用当然很棒，但 QA 团队最初应该如何将他们的分支放入远程的 `qa/` 命名空间呢？
+我们可以通过引用规格推送来完成这个任务。
 
-If the QA team wants to push their `master` branch to `qa/master` on the remote server, they can run
+如果 QA 团队想把他们的 `master` 分支推送到远程服务器的 `qa/master` 分支上，可以运行：
 
 [source,console]
 ----
 $ git push origin master:refs/heads/qa/master
 ----
 
-If they want Git to do that automatically each time they run `git push origin`, they can add a `push` value to their config file:
+如果他们希望 Git 每次运行 `git push origin` 时都像上面这样推送，可以在他们的配置文件中添加一条 `push` 值：
 
 [source,ini]
 ----
@@ -118,15 +118,15 @@ If they want Git to do that automatically each time they run `git push origin`,
 	push = refs/heads/master:refs/heads/qa/master
 ----
 
-Again, this will cause a `git push origin` to push the local `master` branch to the remote `qa/master` branch by default.
+正如刚才所指出的，这会让 `git push origin` 默认把本地 `master` 分支推送到远程 `qa/master` 分支。
 
-==== Deleting References
+==== 删除引用
 
-You can also use the refspec to delete references from the remote server by running something like this:
+你还可以借助类似下面的命令通过引用规格从远程服务器上删除引用：
 
 [source,console]
 ----
 $ git push origin :topic
 ----
 
-Because the refspec is `<src>:<dst>`, by leaving off the `<src>` part, this basically says to make the topic branch on the remote nothing, which deletes it.
+因为引用规格（的格式）是 `<src>:<dst>`，所以上述命令把 `<src>` 留空，意味着把远程版本库的 `topic` 分支定义为空值，也就是删除它。

status.json

@@ -104,7 +104,7 @@
       "sections/packfiles.asc": 0,
       "sections/plumbing-porcelain.asc": 100,
       "sections/refs.asc": 100,
-      "sections/refspec.asc": 0,
+      "sections/refspec.asc": 100,
       "sections/transfer-protocols.asc": 0
     },
     "A-git-in-other-environments": {