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
There are (at least) two different cases where you might use git-svn. One is if you have a project currently stored in an svn repository, and you want to stop using that one, and switch to a git repository (e.g. You decided you hate sourceforge and love github). If you're trying to do this, the gitbook already does a pretty good job of telling you what you need to know.
The second is where you are going to continue hosting the project in an svn repository (for example, because it's for work, and your company is committed* to sticking with svn), but you want to use git locally. This second case is not covered well by the gitbook right now.
The following are some pages that I've found useful in this second case, so maybe, if we get the authors' permission, the information there could be brought into the gitbook.
https://git.wiki.kernel.org/index.php/GitSvnCrashCourse (this last one I don't like so much because it tries to draw parallels between git commands and the "equivalent" svn commands, when in fact they are often not really equivalent)
* pun intended
The text was updated successfully, but these errors were encountered:
There are (at least) two different cases where you might use git-svn. One is if you have a project currently stored in an svn repository, and you want to stop using that one, and switch to a git repository (e.g. You decided you hate sourceforge and love github). If you're trying to do this, the gitbook already does a pretty good job of telling you what you need to know.
The second is where you are going to continue hosting the project in an svn repository (for example, because it's for work, and your company is committed* to sticking with svn), but you want to use git locally. This second case is not covered well by the gitbook right now.
The following are some pages that I've found useful in this second case, so maybe, if we get the authors' permission, the information there could be brought into the gitbook.
* pun intended
The text was updated successfully, but these errors were encountered: