From: Erik Faye-Lund <kusmabite@googlemail.com>
To: git@vger.kernel.org
Subject: git-svn: incomplete data after terminated "git svn clone"
Date: Tue, 10 Feb 2009 12:50:36 +0100 [thread overview]
Message-ID: <40aa078e0902100350m2d885516o853b1ec56eb43ce1@mail.gmail.com> (raw)
I'm a novice at Git, so bear with me even if the answer is obvious to
experienced users, please :)
I recently tried to clone an existing (very big) SVN repo by using
"git svn clone <repo> -s", and by mistake I pressed Ctrl-C after the
clone operation had been running for ~16 hours. When trying to
re-issue the clone, I got the error message "Incomplete data: Delta
source ended unexpectedly at /home/erifay01/libexec/git-core/git-svn
line 4249" after git-svn fetching another 8 or so revisions. Now, I
realize I shouldn't have done this, but I'd still prefer avoiding to
have to re-do it all.
I already tried re-building the svn metadata by moving away ".git/svn"
and re-issuing the clone command, but no luck. It quickly re-builds
everything up to the revision that git-svn broke at, but fails with
the same error message.
Now, I'm wondering if there's any way of going back to the state
before I pressed Ctrl-C, so I can rebuild from there. I know what
revision I terminated at, and I have the corresponding SHA.
--
Erik "kusma" Faye-Lund
kusmabite@gmail.com
(+47) 986 59 656
next reply other threads:[~2009-02-10 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 11:50 Erik Faye-Lund [this message]
2009-02-10 13:42 ` git-svn: incomplete data after terminated "git svn clone" Thomas Rast
2009-02-10 15:01 ` Erik Faye-Lund
2009-02-10 15:10 ` Luciano Miguel Ferreira Rocha
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=40aa078e0902100350m2d885516o853b1ec56eb43ce1@mail.gmail.com \
--to=kusmabite@googlemail.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;
as well as URLs for NNTP newsgroup(s).