Git-svn: Difference between revisions
From Freephile Wiki
Created page with "If you use <code>git-svn</code> (don't, use reposurgeon) to convert to git you'll want to be aware of the --prefix option to <code>git init</code>. From the [https://git-..." |
m formatting |
||
| Line 1: | Line 1: | ||
If you use <code>git-svn</code> (don't, use [[reposurgeon]]) to convert to git you'll want to be aware of the --prefix option to <code>git init</code>. From the [https://git-scm.com/docs/git-svn the manual] | If you use <code>git-svn</code> (don't, use [[reposurgeon]]) to convert to git you'll want to be aware of the --prefix option to <code>git init</code>. From the [https://git-scm.com/docs/git-svn the manual] | ||
< | <blockquote> | ||
--prefix=<prefix> | --prefix=<prefix><br /> | ||
This allows one to specify a prefix which is prepended to the names of remotes if trunk/branches/tags are specified. The prefix does not automatically include a trailing slash, so be sure you include one in the argument if that is what you want. If --branches/-b is specified, the prefix must include a trailing slash. Setting a prefix (with a trailing slash) is strongly encouraged in any case, as your SVN-tracking refs will then be located at "refs/remotes/$prefix/", which is compatible with Git�s own remote-tracking ref layout (refs/remotes/$remote/). Setting a prefix is also useful if you wish to track multiple projects that share a common repository. By default, the prefix is set to origin/. | This allows one to specify a prefix which is prepended to the names of remotes if trunk/branches/tags are specified. The prefix does not automatically include a trailing slash, so be sure you include one in the argument if that is what you want. If --branches/-b is specified, the prefix must include a trailing slash. Setting a prefix (with a trailing slash) is strongly encouraged in any case, as your SVN-tracking refs will then be located at "refs/remotes/$prefix/", which is compatible with Git�s own remote-tracking ref layout (refs/remotes/$remote/). Setting a prefix is also useful if you wish to track multiple projects that share a common repository. By default, the prefix is set to origin/. | ||
Note | Note | ||
Before Git v2.0, the default prefix was "" (no prefix). This meant that SVN-tracking refs were put at "refs/remotes/*", which is incompatible with how Git�s own remote-tracking refs are organized. If you still want the old default, you can get it by passing --prefix "" on the command line (--prefix="" may not work if your Perl�s Getopt::Long is < v2.37). | Before Git v2.0, the default prefix was "" (no prefix). This meant that SVN-tracking refs were put at "refs/remotes/*", which is incompatible with how Git�s own remote-tracking refs are organized. If you still want the old default, you can get it by passing --prefix "" on the command line (--prefix="" may not work if your Perl�s Getopt::Long is < v2.37). | ||
</ | </blockquote> | ||
