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

Re: git svn dcommit crashed -- how do I resume?

From
TLTeemu Likonen <tlikonen@iki.fi>
Date
Nov 26, 2008, 09:42 UTC
Message-ID
<87k5aqlt70.fsf@iki.fi>
In-Reply-To
<E8293DEF-109A-4F57-BD4F-7F189976DA79@gmx.de>
Jens Neuhalfen (2008-11-26 09:22 +0100) wrote:
> 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).
> 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.

I don't know why the the dcommit crashed but I'm certain that you can find your previous commits through the reflog. Try (one of) these commands:

    git log --walk-reflogs [branchname]
    git log --walk-reflogs HEAD

They will show a list of commits about where [branchname] or HEAD has been previously in _your_ repository. If/when you find the correct commit (where you think the branch's head should be) copy its SHA1 and create a new branch from it (git branch new-branch [SHA1]) - or just reset the broken branch to that commit (git reset --hard [SHA1]).

Previous: Jens Neuhalfen
Message 2 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.