git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Klaus <klaus3b-gu@yahoo.de>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: git-svn clone --stdlayout causes "fatal: refs/remotes/trunk: not a valid SHA1"
Date: Mon, 1 Nov 2010 13:14:59 -0500	[thread overview]
Message-ID: <20101101181459.GA9387@burratino> (raw)
In-Reply-To: <20101101171141.GA8853@burratino>

Jonathan Nieder wrote:

> 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

      reply	other threads:[~2010-11-01 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <225342.86075.qm@web24105.mail.ird.yahoo.com>
2010-11-01 17:11 ` git-svn clone --stdlayout causes "fatal: refs/remotes/trunk: not a valid SHA1" Jonathan Nieder
2010-11-01 18:14   ` Jonathan Nieder [this message]

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=20101101181459.GA9387@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=klaus3b-gu@yahoo.de \
    --cc=normalperson@yhbt.net \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).