Re: Bad objects error since upgrading GitHub servers to 1.6.1

On Wed, Jan 28, 2009 at 12:22:01AM -0800, Junio C Hamano wrote:

Nah, I take that back.

Even the original code does not consider this case an error.

If you really want that, the revision machinery needs major surgery, as I
already noted that the design of mark_parents_uninteresting() wants to
treat a missing uninteresting commit as a non-error event.

Hrm. Never mind my concern, then. I was worried that we were losing some
existing corruption checks, but it seems they are not there in the first
place.

-Peff