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:
signature.asc
Description: This is a digitally signed message part