I don't have an svn server using ssh at my disposal, unfortunately, so I was unable to confirm it myself. And I couldn't find definitive documentation on the issue either. But the difference between you and me is that you *have*tried svn+ssh, while I have not. :)
- Jim On Tue, Jun 3, 2008 at 6:35 PM, Edward Z. Yang < [EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jim Raden wrote: > > I don't think that's true, certainly not for http URL's. For > > instance, the example in the man page > > (http://www.kernel.org/pub/software/scm/git/docs/git-svn.html) is > > this: > > > > git-svn clone http://svn.foo.org/project/trunk > > > > Do you mean that "svn+ssh" URLs must end in slashes? Could you cite > > your source? > > Personal experience, really. I've had the error bite me before, and that > was exactly the culprit (it was for a pure ssh URL, however). Also, the > meaning of "Bad File Number" is: > > > The specified file handle is not a valid file-handle value or does > > not refer to an open file. Or an attempt was made to write to a file > > or device opened for read-only access (or vice versa). > > So if it's not the trailing slash, he should check his path and see if > it's accessible. > > - -- > Edward Z. Yang GnuPG: 0x869C48DA > HTML Purifier <http://htmlpurifier.org> Anti-XSS Filter > [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIRcc8qTO+fYacSNoRAnA6AJ9XbkxnQAf1er1bpYH7VE5h3ov2vQCfSF01 > LYcnzN2jWQudElOYebuK1DE= > =aM11 > -----END PGP SIGNATURE----- >
