Timothy Kretschmer venit, vidit, dixit 18.01.2013 17:59:
> The exact names of the branches are "CMT_PHASE3" and
Just to be sure, not to doubt you: the svn branch name is
"BlueSimViewer5.0_20110316_Branch" and thus differs from the name
reported by git-svn? Are there maybe unprintable characters/control
codes or something in the svn branch name?
Somehow, git-svn is using an improper refname.
> File system on the converting machine is ext4. SVN server is hosted on
> a Fedora 8 box , running subversion 1.4.x.
> To move forward, I commented out the problematic branches under
> .git/packed-refs. Conversion continued but skipped the troubled
> Still on the road of finding a way to include those branches in the
> On Fri, Jan 18, 2013 at 11:48 AM, Michael J Gruber
> <g...@drmicha.warpmail.net> wrote:
>> Timothy Kretschmer venit, vidit, dixit 16.01.2013 15:06:
>>> I am seeing the following output while converting a subversion repo to git.
>>> >Found possible branch point: <repo-url>/trunk =>
>>> <repo-url>/branches/CMT_PHASE3, 18441
>>>> fatal: Not a valid object name refs/remotes/BlueSimViewer 5.0 20110316
>>>> cat-file commit refs/remotes/BlueSimViewer 5.0 20110316 Branch: command
>>>> returned error: 128
>>> The command I am running to convert the repo is
>>>> git svn clone <repo-url> -A authors-transform.txt --stdlayout bluebox-git
>>>> > svnlist
>>> I am running git version 188.8.131.52 on an Ubuntu 12.10 server. I am happy
>>> to provide any other information that would be helpful.
>>> I appreciate any assistance you can provide in this matter,
>> git-svn should cope with funky branch names. What is the exact name of
>> the "CMT..." and "BlueSimViewer..." branches? Are you using a case
>> challenged file system or just some standard linux fs?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html