Git development
 help / color / mirror / Atom feed
From: "Carlos Martín Nieto" <cmn@elego.de>
To: Marko Vukovic <amasniko@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Core dump on commit
Date: Mon, 15 Aug 2011 18:11:38 +0200	[thread overview]
Message-ID: <1313424698.12213.1.camel@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <loom.20110815T180732-236@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

On Mon, 2011-08-15 at 16:09 +0000, Marko Vukovic wrote:
> Nguyen Thai Ngoc Duy <pclouds <at> gmail.com> writes:
> 
> > 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
> 
> Thank you very much, I was able to commit after the reset.
> 
> I shall remember never to use eGit for tagging in the future!

A (probably) more useful way to deal with it would be to report a bug to
EGIT so they know about it and can fix it.

Cheers,
   cmn


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-08-15 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 14:30 Core dump on commit Marko Vukovic
2011-08-15 14:41 ` Michael Witten
2011-08-15 15:02   ` Marko Vukovic
2011-08-15 15:12 ` Nguyen Thai Ngoc Duy
2011-08-15 15:48   ` Marko Vukovic
2011-08-15 16:03     ` Nguyen Thai Ngoc Duy
2011-08-15 16:09       ` Marko Vukovic
2011-08-15 16:11         ` Carlos Martín Nieto [this message]
2011-08-15 15:26 ` Nguyen Thai Ngoc Duy
2011-08-15 15:55   ` Marko Vukovic

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=1313424698.12213.1.camel@centaur.lab.cmartin.tk \
    --to=cmn@elego.de \
    --cc=amasniko@yahoo.com \
    --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