From: Michael J Gruber <git@drmicha.warpmail.net>
To: Yaroslav Halchenko <debian@onerussian.com>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: git-svn of both trunk and tags while having no access to the 'parent' of those
Date: Wed, 18 Nov 2009 16:07:01 +0100 [thread overview]
Message-ID: <4B040D95.9040901@drmicha.warpmail.net> (raw)
In-Reply-To: <20091118142332.GC17964@onerussian.com>
Yaroslav Halchenko venit, vidit, dixit 18.11.2009 15:23:
>
> On Wed, 18 Nov 2009, Michael J Gruber wrote:
>>> git svn clone --no-minimize-url --prefix=upstream-svn/ -T trunk -t releases http://domain.com/svnrepo/trunk svnrepo.gitsvn
>> Is the trunk really at svnrepo/trunk/trunk?
> nope... it is just svnrepo/trunk but if I set url to point to parent --
> git svn seeks authentication right away
>
>> I would try both
>> git svn clone --no-minimize-url --prefix=upstream-svn/ -T trunk -t
>> releases http://domain.com/svnrepo/ svnrepo.gitsvn
>
> asks for authentication since there is no public access to
> http://domain.com/svnrepo/
>
>> and also the seemingly equivalent
>
>> git svn clone --no-minimize-url --prefix=upstream-svn/ -T
>> http://domain.com/svnrepo/trunk -t http://domain.com/svnrepo/releases
>> svnrepo.gitsvn
> seems to not work since it wants url as a parameter
>
> Bad URL passed to RA layer: Illegal repository URL svnrepo.gitsvn at /usr/lib/git-core/git-svn line 940
>
>> Also, I assume you can svn list http://domain.com/svnrepo/trunk and
>> http://domain.com/svnrepo/releases ;)
> yeap -- I can list both of those but not their parent.
>
>
OK, so the way it's implemented --no-minimize-url might be half as
useful as it could be. One last try (before asking Eric...) would be
git svn clone --no-minimize-url --prefix=upstream-svn/ -T
http://domain.com/svnrepo/trunk -t http://domain.com/svnrepo/releases
http://domain.com/svnrepo/trunk svnrepo.gitsvn
because that involves accessible URLs only and trunk and branch URLs are
absolute.
[Meanwhile I git the actual URL PMed by Yaroslov.]
So, what happens with the above is that git-svn tries to set the URL
config again from the URL part of an absolute tags argument. I don't
know how absolute URLs (which are documented) for tags etc. could
possibly work if git-svn tries to do that. Eric?
I tried also with two svn sections to circumvent this:
[svn-remote "svn"]
url = http://domain.com:/project/trunk
fetch = :refs/remotes/trunk
[svn-remote "svnr"]
url = http://domain.com:/project/releases
tags = /*:refs/remotes/tags/*
Fetching -Rsvn works fine, but fetching -Rsvnr gives the same
authentication problems. And fetch does not accept --no-minimize-url as
an option. OTOH: If the option is not used it seems to me (from the
source) that not minimizing is the default, which leaves me really
stomped. Eric?? ;)
Michael
next prev parent reply other threads:[~2009-11-18 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 2:59 git-svn of both trunk and tags while having no access to the 'parent' of those Yaroslav Halchenko
2009-11-18 9:01 ` Michael J Gruber
2009-11-18 13:32 ` Yaroslav Halchenko
2009-11-18 13:56 ` Michael J Gruber
2009-11-18 14:23 ` Yaroslav Halchenko
2009-11-18 15:07 ` Michael J Gruber [this message]
2009-11-19 9:53 ` Eric Wong
2009-11-20 20:47 ` Eric Wong
2009-11-22 23:39 ` [PATCH] git svn: always reuse existing remotes on fetch 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=4B040D95.9040901@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=debian@onerussian.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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.