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

Re: git-svn clone --stdlayout causes "fatal: refs/remotes/trunk: not a valid SHA1"

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 1, 2010, 18:14 UTC
Message-ID
<20101101181459.GA9387@burratino>
In-Reply-To
<20101101171141.GA8853@burratino>
Jonathan Nieder wrote:
Show 6 quoted lines
> Is your repository public?  If not, could you give a sketch of the project
> history, for example by running
>
>  $ git log --oneline --name-status
>
> from a successful (non-stdlayout) clone?

Since your trunk directory is called "trunc" rather than "trunk", it seems stdlayout is not appropriate for the import.

There is also a tag named "trunc".  Not sure how that will work out. :(

Anyway, hopefully that information can help interested people to reproduce this problem, document it, and make it fail with a better error message.

For your import, perhaps
	--trunk=<trunk dir> \
	--tags=<tags dir>
would give better results?

If this is a one-time conversion (i.e., it will not need to be updated with later changes from svn), then you might also find some of the methods described in

 http://thread.gmane.org/gmane.comp.version-control.git/158940/focus=159054

helpful (especially use of "git filter-branch" to extract subdirectories from a simple whole-tree import).

Hope that helps, Jonathan

Previous: Jonathan Nieder
Message 2 of 2 in “Re: git-svn clone --stdlayout causes "fatal: refs/remotes/trunk: not a valid SHA1"”
  1. Jonathan NiederNov 1, 2010
  2. Jonathan NiederNov 1, 2010

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.