You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/09-git-and-other-scms/sections/import-svn.asc
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,10 +104,7 @@ $ for t in $(git for-each-ref --format='%(refname:short)' refs/remotes/tags); do
104
104
$ 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
105
105
----
106
106
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:
0 commit comments