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

git-svn dcommit gone wrong and git-fsck

From
BHBruno Harbulot <bruno.harbulot@manchester.ac.uk>
Date
Aug 26, 2008, 16:37 UTC
Message-ID
<g91bgi$8cm$1@ger.gmane.org>
Hello,

I had 11 consecutive commits in my local git repository that I was trying to commit to an SVN repository, using "git-svn dcommit". The first 7 worked fine, as usual. However, when sending the 8th, I got a "Bus error" (on OSX -- I'm not sure what the actual cause was).

A further "git-svn dcommit" produces this error.
Cannot dcommit with a dirty index.  Commit your changes first, or stash 
them with `git stash'.
  at /opt/local/bin/git-svn line 406

In addition, "gitk --all" no longer shows commits 8->11, but the current files seem to correspond to the last local commit. I've run git-fsck which shows 3 dangling trees and about a dozen dangling blobs.

Apologies if it's a FAQ, but I can't seem to find much documentation on how this can be fixed (if it can). Is there a way to recover the missing commits and re-attach them back on the branch? (I had pushed that branch up to the 10th commit into another repository, which could help.)

Thank you,
Bruno.
Next: Björn Steinbrink
Message 1 of 3 in “git-svn dcommit gone wrong and git-fsck”
  1. Bruno HarbulotAug 26, 2008
  2. Björn SteinbrinkAug 26, 2008
  3. Bruno HarbulotAug 26, 2008

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.