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

git svn dcommit crashed -- how do I resume?

From
JNJens Neuhalfen <jensneuhalfen@gmx.de>
Date
Nov 26, 2008, 08:22 UTC
Message-ID
<E8293DEF-109A-4F57-BD4F-7F189976DA79@gmx.de>
Hi,

I am using git as a frontend to my SVN-Repository. When I tried to "git svn dcommit" several changes from my local git-repository, git crashed (SEGFAULT, AFAIR).

Now I have a working copy (master branch) that points "somewhere in the past" (at least my files are old). I have a git-svn remote branch that points to the same SHA1.

$ git branch -a
   dokument-zusammenfuehren
* master
   git-svn
I cannot dcommit
$ git svn dcommit
Cannot dcommit with a dirty index.  Commit your changes first, or  
stash them with `git stash'.
  at /Users/jens/libexec/git-core/git-svn line 415
And, indeed, the index is dirty.

I am confused (an slightly panicked), because my old commits seem to be "gone", my WC does not contain the most recent files and there seems to be no "backup-branch" with my old HEAD.

Any idea, how I might get my data back and how to 'resume' the dead dcommit? Google did not turn up anything usefull, unfortunally.

BTW: I am currently using git version 1.6.0.rc0.24.gf45e0.dirty.
Jens
Next: Teemu Likonen
Message 1 of 2 in “git svn dcommit crashed -- how do I resume?”
  1. Jens NeuhalfenNov 26, 2008
  2. Teemu LikonenNov 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.