public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Daniel Cordero <theappleman@gmail•com>
To: Adam Brewster <adambrewster@gmail•com>,
	Eric Wong <normalperson@yhbt•net>
Cc: git@vger•kernel.org
Subject: [bug][bisected] git-svn with root branches
Date: Wed, 21 Oct 2009 15:41:13 +0100	[thread overview]
Message-ID: <20091021144113.GA7440@cumin> (raw)

Hello,

when trying to clone a svn repo with the command-line:

	$ git svn clone -b / http://svn.collab.net/repos/svn/

(that is, each folder in the root of the repo should be considered it's
own branch)
the clone sometimes[1] fails saying:

	ref: 'refs/remotes/' ends with a trailing slash, this is not permitted by git nor Subversion

The offending config is:
[svn-remote "svn"]
        url = http://svn.collab.net/repos/svn
        branches = /*:refs/remotes/*


This used to work in the past; I bisected the bad commit to

commit 6f5748e14cc5bb0a836b649fb8e2d6a5eb166f1d
Author: Adam Brewster <adambrewster@gmail•com>
Date:   Tue Aug 11 23:14:03 2009 -0400

    svn: allow branches outside of refs/remotes


Thanks in advance.


[1] It does work when the URL has at least 1 folder of depth
(e.g. suffix "trunk" to the above URL).

Its config section is:
[svn-remote "svn"]
        url = http://svn.collab.net/repos/svn
	branches = trunk//*:refs/remotes/*

next             reply	other threads:[~2009-10-21 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 14:41 Daniel Cordero [this message]
2009-10-22  6:30 ` [bug][bisected] git-svn with root branches Eric Wong
     [not found]   ` <c376da900910220824g2948dc2sa1156bda59b49405@mail.gmail.com>
2009-10-22 18:55     ` Eric Wong
2009-10-23  6:38     ` Eric Wong
2009-10-23  4:48 ` [PATCH] git svn: fix fetch where glob is on the top-level URL Eric Wong
2009-10-23  6:07   ` Eric Wong
2009-10-23  6:50     ` 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=20091021144113.GA7440@cumin \
    --to=theappleman@gmail$(echo .)com \
    --cc=adambrewster@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=normalperson@yhbt$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox