All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yaroslav Halchenko <debian@onerussian.com>
To: git@vger.kernel.org
Subject: git-svn of both trunk and tags while having no access to the 'parent' of those
Date: Mon, 16 Nov 2009 21:59:45 -0500	[thread overview]
Message-ID: <20091117025945.GE17964@onerussian.com> (raw)

Dear Git People,

I've ran into a situation here:

there is a repository with trunk and releases (analog to tags there)
available for public, but the rest of directories and their parent is
not available without authentication... ie I can access

http://domain.com/svnrepo/trunk
http://domain.com/svnrepo/releases
but not
http://domain.com/svnrepo/

Whenever I use git-svn (1.6.5 in Debian):

git svn clone --prefix=upstream-svn/ -T trunk -t releases http://domain.com/svnrepo svnrepo.gitsvn

it asks for authentication... I guess, now I can only clone trunk and
releases separately? or may be there is some way to avoid the
problem, ie avoid looking 'into root'?

Thanks in advance!
-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik        

             reply	other threads:[~2009-11-17  3:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17  2:59 Yaroslav Halchenko [this message]
2009-11-18  9:01 ` git-svn of both trunk and tags while having no access to the 'parent' of those 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
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=20091117025945.GE17964@onerussian.com \
    --to=debian@onerussian.com \
    --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.