public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro•com>
To: git@vger•kernel.org
Subject: Possible issue with git svn-remote.<name>.rewriteRoot?
Date: Mon, 11 Apr 2011 11:48:17 -0400	[thread overview]
Message-ID: <m2oc4cvlfi.wl%dave@boostpro.com> (raw)


Hi All,

my 

  git svn fetch

command just ended abruptly with

  Found possible branch point: file:///home/subversion/boost/branches/unlabeled-1.1.1 => file:///home/subversion/boost/tags/release_1_16_1, 7620
  refs/remotes/trunk: 'file:///home/subversion/boost' not found in 'https://svn.boost.org/svn/boost/trunk'


I am using git 1.7.3.4 and my .git/config reads as follows:

---------<schnipp>---------
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[svn-remote "svn"]
	rewriteRoot = https://svn.boost.org/svn/boost
	url = file:///home/subversion/boost
	fetch = trunk:refs/remotes/trunk
	branches = branches/*:refs/remotes/*
	tags = tags/*:refs/remotes/tags/*
	branches = branches/*:refs/remotes/*
	tags = tags/*:refs/remotes/tags/*
[svn]
        authorsfile=authors.txt
---------<schnapp>---------

Is this a bug, expected behavior, or...?

Thanks!

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

                 reply	other threads:[~2011-04-11 15:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m2oc4cvlfi.wl%dave@boostpro.com \
    --to=dave@boostpro$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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