From: Jonathan Nieder <jrnieder@gmail.com>
To: Joey Hess <joey@kitenet.net>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Shilong Wang <wangshilong1991@gmail.com>,
git@vger.kernel.org, Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Subject: Re: [Question] Git recovery with HEAD commit broken
Date: Wed, 11 Dec 2013 11:12:07 -0800 [thread overview]
Message-ID: <20131211191207.GL2311@google.com> (raw)
In-Reply-To: <20131211161407.GA15939@kitenet.net>
Joey Hess wrote:
> [2] A particularly annoying one is that git branch -d cannot be used
> to remove a branch that is directly pointing to a corrupted commit!
It's generally considered okay for everyday commands like "git branch -d"
not to cope well with corrupted repositories, but we try to keep
plumbing like "git update-ref -d" working to give people a way out.
Is update-ref -d broken in this situation, too?
Curious,
Jonathan
prev parent reply other threads:[~2013-12-11 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:38 [Question] Git recovery with HEAD commit broken Shilong Wang
2013-12-11 15:01 ` Matthieu Moy
2013-12-11 16:14 ` Joey Hess
2013-12-11 19:12 ` Jonathan Nieder [this message]
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=20131211191207.GL2311@google.com \
--to=jrnieder@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.net \
--cc=wangshilong1991@gmail.com \
--cc=wangsl.fnst@cn.fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).