From: "Florian Köberle" <florian@fkoeberle.de>
To: git@vger.kernel.org
Subject: [BUG REPORT] git-svn fails to create branches if ssh+svn gets used as protocol.
Date: Tue, 22 Dec 2009 10:53:52 +0100 [thread overview]
Message-ID: <4B309730.5070509@fkoeberle.de> (raw)
Hello
I haven't seen a link to a bug tracker so I am sending this bug report
to the mailing list, I hope it's okay.
If you try to run
$ git svn branch foo
in a project using a svn+ssh url, you get the following error log:
Copying svn+ssh://example.org/svn/project/trunk at r1000 to
svn+ssh://me@example.org/svn/project/branches/foo...
Trying to use an unsupported feature: Source and dest appear not to be
in the same repository (src: 'svn+ssh://example.org/svn/project/trunk';
dst: 'svn+ssh://me@example.org/svn/project/branches/foo') at
/home/florian/libexec/git-core/git-svn line 722
It fails as the username is missing in the source url. If you modify the
git-svn script and add the username it works. The bug can be reproduced
with git-svn version 1.6.5.7 (svn 1.5.1).
Best regards,
Florian
next reply other threads:[~2009-12-22 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 9:53 Florian Köberle [this message]
2009-12-23 7:25 ` [BUG REPORT] git-svn fails to create branches if ssh+svn gets used as protocol Eric Wong
2009-12-23 19:26 ` Florian Köberle
2009-12-23 20:03 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B309730.5070509@fkoeberle.de \
--to=florian@fkoeberle.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.