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

Re: Core dump on commit

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Aug 15, 2011, 16:03 UTC
Message-ID
<CACsJy8BBvgJauL4a9MxWAXGN-_qiAKprt15hizyBp0O9knwKrg@mail.gmail.com>
In-Reply-To
<loom.20110815T172423-956@post.gmane.org>
On Mon, Aug 15, 2011 at 10:48 PM, Marko Vukovic <amasniko@yahoo.com> wrote:
> Pardon my ignorance, but what does "git reset" do? I have got some uncommitted
> changes in the staging area. What will happen to them?

I should have written "git reset --soft 1b9a976133", which resets HEAD ref back to (assuming) good commit. See [1] for more information. I think for some reason, eGit put a tag object to HEAD, while it should be a commit object. By resetting it back to the commit that the tag points to, you may be able to commit again.

No history would be lost. Also if you use --soft, index should be untouched. As always, back up your repository (copy the whole directory, including .git) before doing anything.

[1] http://www.kernel.org/pub/software/scm/git/docs/git-reset.html
-- 
Duy
Previous: Marko VukovicNext: Marko Vukovic
Message 6 of 10 in “Core dump on commit”
  1. Marko VukovicAug 15, 2011
  2. Michael WittenAug 15, 2011
  3. Marko VukovicAug 15, 2011
  4. Nguyen Thai Ngoc DuyAug 15, 2011
  5. Marko VukovicAug 15, 2011
  6. Nguyen Thai Ngoc DuyAug 15, 2011
  7. Marko VukovicAug 15, 2011
  8. Carlos Martín NietoAug 15, 2011
  9. Nguyen Thai Ngoc DuyAug 15, 2011
  10. Marko VukovicAug 15, 2011

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.