From: Michael Haggerty <mhagger@alum.mit.edu>
To: Zheng Zhang <simsicon@gitcafe.com>, git@vger.kernel.org
Cc: GitCafe-dev-team <dev@gitcafe.com>
Subject: Re: Bad object pointed under refs/head/
Date: Sat, 14 Feb 2015 07:19:10 +0100 [thread overview]
Message-ID: <54DEE8DE.9060501@alum.mit.edu> (raw)
In-Reply-To: <CAN6kTyfiw6QPk469xV6gyL-+YB5Ca3vNHhEX7daiyn7j536SXQ@mail.gmail.com>
On 02/13/2015 11:06 AM, Zheng Zhang wrote:
> I was running some test with Git 1.8.4.5, then I accidentally met a
> problem that leaded to the following error,
>
>>> error: refs/heads/develop does not point to a valid object!
>
> Turns out that the sha in refs/heads/develop is a bad object id, this
> happened after merging a branch X to branch develop, but packed-refs
> is updated to a corrected sha. No other merges at that point.
>
> The fix is easy, just removed refs/heads/develop.
>
> So there were two sha created, one is updated to refs/heads/develop,
> and the other one which is corrected, updated to packed-refs, Weird.
>
> I am wondering if there is a way to prevent this happening? Is this an
> ancient bug?
If you can find and document a way to reproduce this problem, then you
will have a much better chance of finding somebody who is willing to
look into it. Otherwise it's hard to know how to even get started.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
prev parent reply other threads:[~2015-02-14 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 10:06 Bad object pointed under refs/head/ Zheng Zhang
2015-02-14 6:19 ` Michael Haggerty [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=54DEE8DE.9060501@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=dev@gitcafe.com \
--cc=git@vger.kernel.org \
--cc=simsicon@gitcafe.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).