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

[PATCH] Use a relative path for SVN importing

From
CBChristian Biesinger <cbiesinger@web.de>
Date
Feb 11, 2006, 15:44 UTC
Message-ID
<1139672651713-git-send-email-cbiesinger@web.de>

The absolute path (with the leading slash) breaks SVN importing, because it then looks for /trunk/... instead of /svn/trunk/... (in my case, the repository URL was https://servername/svn/)

Signed-off-by: Christian Biesinger <cbiesinger@web.de>
---
 git-svnimport.perl |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
7718b5a5fec01c0774f6b9cdc84f908e68b403ac
diff --git a/git-svnimport.perl b/git-svnimport.perl
index b6799d8..f17d5a2 100755
--- a/git-svnimport.perl
+++ b/git-svnimport.perl
@@ -318,7 +318,7 @@ sub get_file($$$) {
 			die $res->status_line." at $url\n";
 		}
 	} else {
-		$name = $svn->file("/$svnpath",$rev);
+		$name = $svn->file("$svnpath",$rev);
 		return undef unless defined $name;
 	}
 
-- 
1.1.6.g486a-dirty
Next: Christian Biesinger
Message 1 of 3 in “Use a relative path for SVN importing”
  1. Use a relative path for SVN importingChristian Biesinger, Feb 11, 2006
  2. Christian BiesingerFeb 11, 2006
  3. git-svnimport -d and -D options (was Re: [PATCH] Use a relative path for SVN importing)Eduardo Pereira Habkost, Feb 13, 2006

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.