Spaces in remotes and git annex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hi, I seems to be predestined to find strange problems. ;-) Today I cloned a remote git annexed repository that has a space in path. With git I have to use one backslash instead of three that are needed in scp. Now I tried to get a document from that repository and failed as git-annex seems to use scp and need all three backslashes. Is there any way to work around that problem? Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJPBdp3AAoJEKZ8CrGAGfasaa4L/iYWz+qRsa2RiVt0RRWIV4X2 ABm2tFFHJ0pyP/Zguea8omLPYvg5xf1qpIUiKZB1A3DerbxN6IdwgytfXfDX3aKz QSHU0VisgjS2JXxajPXygNqYex8Obomcjj/n/gR9abRInPDwOqllLpL6vVCMzDd+ /xDH53Yocckorvq+oIKUKl8JGZSsyY85hm+Jbveac91RYchTfvqajCBhO/zCVjXl JXwTiovtr3rNQPbf3rxh0XLejGVvPwNWfw3RAz1G8TgKmyzDP1IIQzuVcN5/le9z lq32ve5UaroWQwZHBwsXHVObBV42eQpktV+VPDSOCS8SnIoXNbpYvR4GhxF1Rz6x uuGCy128LxW6xjksxqbjlnFpYMDaiz7ZuKfK6IolU/LrQu0k3b5JJBp+1fJ3tCBB zX4D/TMjJJ0uf1dUfXCrGBG9zaYf4rH24R12WORz8rM6wHhkEEbYFXufD2TWnH6f X6ZH+HZXa/SSAKzd9J1WrR9TwamWHIC+vc7ni9Dw2w== =1f+I -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Spaces in remotes and git annex
Klaus Ethgen wrote: I seems to be predestined to find strange problems. ;-) Today I cloned a remote git annexed repository that has a space in path. With git I have to use one backslash instead of three that are needed in scp. Now I tried to get a document from that repository and failed as git-annex seems to use scp and need all three backslashes. Is there any way to work around that problem? I've pushed a change that improves git-annex's support for weird urls like this: url = ssh://localhost/home/joey/tmp/foo bar url = localhost:tmp/foo bar Before, git-annex would seem to ignore the first of these (it actually thought it was a local directory!), and complained the second was a bad url, now both are supported and work in my tests. Maybe this will fix your problem. If not, what kind of repository is it, a git repository, or a special remote, and what does the url for it in .git/config look like? -- see shy jo signature.asc Description: Digital signature ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
