From: "David H. Lynch J.r" <ml@dlasys.net>
To: git@vger.kernel.org
Subject: git svn rebase problem
Date: Fri, 15 May 2009 17:21:09 -0400 [thread overview]
Message-ID: <4A0DDCC5.4010001@dlasys.net> (raw)
For some time I am using git svn to manage a local copy of a remote svn
repository.
The svn repository has no branches.
A few days ago I did an
git svn rebase
The rebase took a while and after it completed reported
fatal: bad object HEAD
git status reports
root@hp-dhlii:/usr/src/pico/git# git status
# Not currently on any branch.
fatal: bad object HEAD
and git fsck reports
root@hp-dhlii:/usr/src/pico/git# git fsck
dangling blob eb3afb4aa3aaf0003bac601a5db4fd76aafa2a87
dangling commit 5c496db25007c17c325f294bb8324097c9bc407d
How can I recover without downloading the entire repository again which
could take days?
next reply other threads:[~2009-05-15 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:21 David H. Lynch J.r [this message]
2009-05-15 23:53 ` git svn rebase problem Avery Pennarun
2009-05-16 3:52 ` John Tapsell
2009-05-18 8:38 ` Matthias Andree
2009-05-18 17:00 ` Avery Pennarun
2009-05-19 0:56 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2009-05-18 14:06 David H. Lynch J.r
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=4A0DDCC5.4010001@dlasys.net \
--to=ml@dlasys.net \
--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).