From 54704e16a34bd37d9ad88abe7efa0b3397f20d0b Mon Sep 17 00:00:00 2001 From: CodingSpiderFox Date: Fri, 18 Oct 2019 08:08:32 +0000 Subject: [PATCH 1/2] Fix formatting --- book/09-git-and-other-scms/sections/import-svn.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/09-git-and-other-scms/sections/import-svn.asc b/book/09-git-and-other-scms/sections/import-svn.asc index 32cbe65c2..72bfb7a53 100644 --- a/book/09-git-and-other-scms/sections/import-svn.asc +++ b/book/09-git-and-other-scms/sections/import-svn.asc @@ -104,7 +104,7 @@ $ for b in $(git for-each-ref --format='%(refname:short)' refs/remotes); do git ---- 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. -This is actually a Subversion feature called ``peg-revisions'', which is something that Git simply has no syntactical counterpart for. +This is actually a Subversion feature called `peg-revisions`, which is something that Git simply has no syntactical counterpart for. 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. If you do not care anymore about the peg-revisions, simply remove them: From bfe080b8781384fef649e40f06d0c602a3406afa Mon Sep 17 00:00:00 2001 From: CodingSpiderFox Date: Sat, 19 Oct 2019 09:12:37 +0000 Subject: [PATCH 2/2] Update import-svn.asc --- book/09-git-and-other-scms/sections/import-svn.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/09-git-and-other-scms/sections/import-svn.asc b/book/09-git-and-other-scms/sections/import-svn.asc index 72bfb7a53..e5bcb0045 100644 --- a/book/09-git-and-other-scms/sections/import-svn.asc +++ b/book/09-git-and-other-scms/sections/import-svn.asc @@ -104,7 +104,7 @@ $ for b in $(git for-each-ref --format='%(refname:short)' refs/remotes); do git ---- 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. -This is actually a Subversion feature called `peg-revisions`, which is something that Git simply has no syntactical counterpart for. +This is actually a Subversion feature called “peg-revisions”, which is something that Git simply has no syntactical counterpart for. 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. If you do not care anymore about the peg-revisions, simply remove them: