git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Gerrit Pape <pape@smarden.org>
Date
Jun 19, 2007, 16:47 UTC
Message-ID
<20070619164741.16352.qmail@1b445471b48f1c.315fe32.mid.smarden.org>

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>
---
 Documentation/git-svn.txt |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index c0d7d95..0a210e4 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -66,9 +66,10 @@ COMMANDS
 	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.  This is useful if
-	you wish to track multiple projects that share a common
-	repository.
+	argument if that is what you want.  If --branches/-b is
+	specified, the prefix must include a trailing slash.
+	Setting a prefix is useful if you wish to track multiple
+	projects that share a common repository.
 
 'fetch'::
 	Fetch unfetched revisions from the Subversion remote we are
-- 
1.5.2.1
Message 1 of 1 in “git-svn: trailing slash in prefix is mandatory with --branches/-b”
  1. git-svn: trailing slash in prefix is mandatory with --branches/-bGerrit Pape, Jun 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.