git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn error when cloning apache repo

From
JXJing Xue <jingxue@digizenstudio.com>
Date
Sep 18, 2007, 12:53 UTC
Message-ID
<20070918125352.GA19524@falcon.digizenstudio.com>
In-Reply-To
<46ED17A9.2010603@vilain.net>
On Sun, Sep 16, 2007 at 11:46:49PM +1200, Sam Vilain wrote:
Show 8 quoted lines
> Jing Xue wrote:
> > $ git svn clone https://svn.apache.org/repos/asf/incubator/ivy/core/ ivy-core -T trunk -b branches -t tags
> > Initialized empty Git repository in .git/
> > Using higher level of URL: https://svn.apache.org/repos/asf/incubator/ivy/core => https://svn.apache.org/repos/asf
> >   
> 
> I'm fairly sure this is where it went wrong. Try editing .git/config and
> putting your original URL in the source URL, and re-try the fetch.

Hmm... thanks, but didn't work. The repo didn't look right to begin with. The HEAD pointed to refs/heads/master as usual, but there was nothing in refs/heads at all.

I also tried: git svn clone https://svn.apache.org/repos/asf/ ivy-core -s --prefix=incubator/ivy/core/

And got no errors, but there wasn't any working tree in ivy-core afterwards. Then I tried 'git svn rebase':

fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions fatal: Needed a single revision invalid upstream

Due to the same "nothing in refs/heads" situation. Also there is this 23M file .git/svn/incubator/ivy/core/trunk/.rev_db.13f79535-47bb-0310-9956-ffa450edef6 that contains all 0's.

The part before "I also tried..." was with git 1.5.3. "I also tried..." was with git 1.5.3.1.112.gb7a2 as of last night.

Cheers.
-- 
Jing Xue
Previous: Sam Vilain
Message 3 of 3 in “git-svn error when cloning apache repo”
  1. Jing XueSep 15, 2007
  2. Sam VilainSep 16, 2007
  3. Jing XueSep 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.