Skip to content

Commit 7d64fb0

Browse files
ousugonetworm
authored andcommitted
update import-svn.asc
1 parent 7ff424b commit 7d64fb0

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

book/09-git-and-other-scms/sections/import-svn.asc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -104,10 +104,7 @@ $ for t in $(git for-each-ref --format='%(refname:short)' refs/remotes/tags); do
104104
$ for b in $(git for-each-ref --format='%(refname:short)' refs/remotes); do git branch $b refs/remotes/$b && git branch -D -r $b; done
105105
----
106106

107-
It may happen that you'll see some extra branches which are suffixed by `@xxx` (where xxx is a number), while in Subversion you only see one branch.
108-
This is actually a Subversion feature called ``peg-revisions'', which is something that Git simply has no syntactical counterpart for.
109-
Hence, `git svn` simply adds the svn version number to the branch name just in the same way as you would have written it in svn to address the peg-revision of that branch.
110-
If you do not care anymore about the peg-revisions, simply remove them:
107+
你可能会看到一些额外的分支,这些分支的后缀是 `@xxx` (其中 xxx 是一个数字),而在 Subversion 中你只会看到一个分支。这实际上是 Subversion 一个叫做“peg-revisions”的功能,Git在语法上没有与之对应的功能。因此, `git svn` 只是简单地将 SVN peg-revision 版本号添加到分支名称中,这同你在 SVN 中修改分支名称来定位一个分支的“peg-revision”是一样的。如果你对于 peg-revisions 完全不在乎,通过下面的命令可以轻易地移除他们:
111108

112109
[source,console]
113110
----

0 commit comments

Comments
 (0)