undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

git-svn: trailing slash in prefix is mandatory with --branches/-b

Browse Source 
Make clear in the documentation that when using --branches/-b and
--prefix with 'init', the prefix must include a trailing slash.
This matches the actual behavior of git-svn, e.g.:

 $ git svn init -Ttrunk -treleases -bbranches --prefix xxx \
     http://svn.sacredchao.net/svn/quodlibet/
 --prefix='xxx' must have a trailing slash '/'
 $

This was noticed by R. Vanicat and reported through
 http://bugs.debian.org/429443

Signed-off-by: Gerrit Pape <pape@smarden.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Gerrit Pape 2007-06-19 16:47:41 +00:00 committed by Junio C Hamano
parent 09381b458f
commit 0d351e9ca2
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Documentation/git-svn.txt
View File

@ -66,9 +66,10 @@ COMMANDS
to the names of remotes if trunk/branches/tags are to the names of remotes if trunk/branches/tags are
specified. The prefix does not automatically include a specified. The prefix does not automatically include a
trailing slash, so be sure you include one in the trailing slash, so be sure you include one in the
argument if that is what you want. This is useful if argument if that is what you want. If --branches/-b is
you wish to track multiple projects that share a common specified, the prefix must include a trailing slash.
repository. Setting a prefix is useful if you wish to track multiple
projects that share a common repository.
'fetch':: 'fetch'::
Fetch unfetched revisions from the Subversion remote we are Fetch unfetched revisions from the Subversion remote we are