Using MacPorts with git 1.7.0.4 and Subversion 1.6.11, ironically, cloning Subversion's own source code is failing. I'm using a larger log window size to make the scan to svn's first commit in the repository much faster: $ git svn clone --log-window-size 5000 -s https://svn.apache.org/repos/asf/subversion It ends up failing with: r855619 = c93a05b8f94c53b8748ffe9352445209fe648e87 (refs/remotes/trunk) M contrib/client-side/svn-clean r855620 = a6b138d3112b1ea0b51b112c6598aae5644369ae (refs/remotes/trunk) M subversion/bindings/swig/core.i M subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c A subversion/bindings/swig/python/libsvn_swig_py/svn_old_swig.h M subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.h M subversion/bindings/swig/include/svn_global.swg M subversion/bindings/swig/include/svn_types.swg r855621 = 41bbc61c035218937f1032381f02c481c8653a22 (refs/remotes/python-bindings-improvements) W:svn cherry-pick ignored (subversion/trunk:855604) - missing 79 commit(s) (eg 462871a2ededa70304eeb99affe550fd029557b5) r855622 = 2c62a0cca702ffe59dabee92220cf28aedfe1c84 (refs/remotes/python-bindings-improvements) fatal: ambiguous argument '3b290983fbd7b401e4d1d20256378ba3657cf7d6^..862ea856c2acad5035ce14758fb928c07d7b7f6b': unknown revision or path not in the working tree. Use '--' to separate paths from revisions rev-list 3b290983fbd7b401e4d1d20256378ba3657cf7d6^..862ea856c2acad5035ce14758fb928c07d7b7f6b: command returned error: 128 I've tried two separate clones with the exact same error. Trying to finish the clone then gets this: $ cd subversion $ git svn fetch && git svn rebase fatal: ambiguous argument '3b290983fbd7b401e4d1d20256378ba3657cf7d6^..862ea856c2acad5035ce14758fb928c07d7b7f6b': unknown revision or path not in the working tree. Use '--' to separate paths from revisions rev-list 3b290983fbd7b401e4d1d20256378ba3657cf7d6^..862ea856c2acad5035ce14758fb928c07d7b7f6b: command returned error: 128 Regards, Blair -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html