From: Piotr Krukowiecki Date: Mon, 07 Feb 2011 11:58:33 GMT Subject: git-svn problems with cloning Message-ID: Hi, I'm trying to git-svn clone repository. I have encountered two problems. For the the first one I have a workaround, but I'm lost with the second. 1. I have a problem with one commit which tries to create a file name which is not acceptable by file system (fat32). I tried to ignore this files by using --ignore-paths, but it does not work. Am I using ignore-paths incorrectly or do I have to find a different workaround? (I'm thinking about using specific revisions or using filter-branch). Here's what's happening: $ git svn clone -s -r164508 '--ignore-paths=.*https:.*' Initialized empty Git repository in /.git/ Using higher level of URL: => mkdir .git/svn/refs/remotes/tags/https:: Invalid argument at /usr/local/stow/git-1.7.4/libexec/git-core/git-svn line 3856 $ svn log -v -r164508 [...] A //tags/https:/blahblah $ mkdir https: mkdir: cannot create directory `https:': Invalid argument 2. I have specified revision that do not have invalid file names in it and it worker, but git reported error later on, I suppose due to --ignore-paths: $ git svn clone -s '--ignore-paths=^/branches/' '--ignore-paths=^/tags/' -r164510:HEAD [...] r166131 = 86085ee643d1b8ecb60f6ec3212904a24dd4d71a (refs/remotes/ ) [...] r167889 = 1fdb8124d72e1bc417f7fe06051a5280675dc73b (refs/remotes/) M [...] Found merge parent (svn:mergeinfo prop): 1fdb8124d72e1bc417f7fe06051a5280675dc73b [...] W: Cannot find common ancestor between 689e9a85f91eb71e37ccd79063e0a5aaa37d1b74 and 5d04d29ab3c76835facade1859aed30129abecf4. Ignoring merge info. Found merge parent (svn:mergeinfo prop): 039125717428084cdf4d38b8a98f431a9b656f1c Couldn't find revmap for //path fatal: ambiguous argument '86085ee643d1b8ecb60f6ec3212904a24dd4d71a^..1fdb8124d72e1bc417f7fe06051a5280675dc73b': unknown revision or path not in the working tree. Use '--' to separate paths from revisions rev-list 86085ee643d1b8ecb60f6ec3212904a24dd4d71a^..1fdb8124d72e1bc417f7fe06051a5280675dc73b: command returned error: 128 I'm not sure how to deal with this... -- Piotrek