Git development
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Esben Skovenborg <esskov@oncable.dk>
Cc: git@vger.kernel.org
Subject: Re: git-svn is "Unable to determine upstream SVN information..."
Date: Fri, 10 Jul 2009 13:33:22 -0700	[thread overview]
Message-ID: <20090710203322.GA18051@dcvr.yhbt.net> (raw)
In-Reply-To: <5m5e55538tlnq40rup7rci61i2mg16q0dv@4ax.com>

Esben Skovenborg <esskov@oncable.dk> wrote:
> On Thu, 9 Jul 2009 20:31:33 -0700, Eric Wong wrote:
> >Are there any weird characters in the URL?  
> 
> No. The only thing 'different' about this svn server is that it uses
> authentication (i.e. asks for name+password). But I suppose that when the
> git-svn fetch goes well, then this is not the problem?  Do the git-svn
> info and git-svn rebase even need to access the svn server?

Yes, rebase (without the -l) option needs it for sure.  I think info can
optionally use it, too.  Does enabling authentication caching (enabled
by default in SVN) help things?  I haven't used the authentication
prompt pieces in ages, they're hard to test in an automated fashion so
they may have bit-rotted since I last looked at them...

> >Off the top of my head I can't think of anything else; I assume
> >you're not allowed to share access to the repo (or to the clone) you're
> >having problems with?
> 
> Right, at least it's something we should talk about off-list.
> 
> Is there any way of asking git-svn *why* it is "unable to determine
> upstream SVN information from working tree history" ?

If you're comfortable with a little Perl, you can sprinkle some debug
statements in working_head_info().  Feel free to email me directly
offlist but my schedule looks pretty hectic today and this weekend
and I may be offline a lot.

-- 
Eric Wong

  reply	other threads:[~2009-07-10 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 22:53 git-svn is "Unable to determine upstream SVN information..." esskov
2009-07-10  3:31 ` Eric Wong
2009-07-10 11:15   ` Esben Skovenborg
2009-07-10 20:33     ` Eric Wong [this message]
2009-07-12 18:58       ` [PATCH] git svn: allow uppercase UUIDs from SVN Eric Wong
2009-07-12 21:15         ` Junio C Hamano
2009-07-12 21:53           ` Junio C Hamano
2009-07-12 21:56             ` 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=20090710203322.GA18051@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=esskov@oncable.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox