On Jun 26, 8:46 pm, "Peter Harris" <[EMAIL PROTECTED]> wrote:
[...] > Peter Harris > (who was going to look at git-svn earlier in the week, but got > distracted by the whole "msys CVS is a year out of date" thing) Terribly sorry about that. I will try to keep version control up-to- date in the future. I took a look myself at git-svn, and this is what I found out: The problem is in path translation. Or, rather, the lack of it. For instance, try something like this: $ touch /tmp/mf8vpEaKoj $ git hash-object -w /tmp/mf8vpEaKoj e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 git doesn't know where /tmp really is (it is actually C:\Documents and Settings\...\Temp). Fortunately, path translation kicks in, and all is well. Now, the current implementation of "hash_and_insert_object" in Git.pm works with pipes, like this: $ echo /tmp/mf8vpEaKoj | git hash-object -w --stdin-paths fatal: Unable to hash /tmp/mf8vpEaKoj The file name is passed by stdin, but MSYS only translates paths on the command line. The path is passed on untranslated. One workaround would be to create the temporary file in the current directory, avoiding the need for path translation. Other than that, git svn clone and git svn dcommit seem to work fine. I will try to come up with a patch. Regards, Cesar
