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 mhag...@alum.mit.edu -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
