Git development
 help / color / mirror / Atom feed
From: Justin Pitts <justinpitts@gmail.com>
To: git@vger.kernel.org
Subject: unable to resume git svn fetch
Date: Fri, 17 Dec 2010 09:28:15 -0500	[thread overview]
Message-ID: <62DF67FC-1C4E-4E65-9B19-B485CDF5EEF6@gmail.com> (raw)

Hello,

I am trying to import a SVN repo that I will be tracking for the foreseeable future.
The clone command was
git svn clone -T trunk -t tags -t release_tags -b branches -b private/branches $REPO

The fetch has been interrupted several times. Up until now I have had no problem resuming with git svn fetch.

Now, fetch fails on r9007 with 
	Incomplete data: Delta source ended unexpectedly at /opt/local/libexec/git-core/git-svn line 5117

I see some messages on the BUG mailing list regarding this error, but I get somewhat lost in the details of the repair and trying to understand how I might apply them to my scenario. Also, 

git svn log
and
git svn reset -r9006
fail with
	fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.

More detail from my shell session is at https://gist.github.com/79e08fe7551875f8bce9

This is git v1.7.3.3 on OSX v1.6.5 via MacPorts. I see that 1.7.3.4 is out, though not in MacPorts yet and nothing in the 
release notes lead me to believe it would be useful, though I am certainly willing to do a source install if it is.

It was suggested in #git that I ought to limit the amount of history I am importing. I think that's a cop-out, but I'll listen to a reasoned argument why that opinion is wrong.

Thanks in advance,

Justin

                 reply	other threads:[~2010-12-17 14:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=62DF67FC-1C4E-4E65-9B19-B485CDF5EEF6@gmail.com \
    --to=justinpitts@gmail.com \
    --cc=git@vger.kernel.org \
    /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