Files
git/builtin
Jeff King c2d17b3b6e fsck: check HAS_OBJ more consistently
There are two spots that call lookup_object() and assume
that a non-NULL result means we have the object:

  1. When we're checking the objects given to us by the user
     on the command line.

  2. When we're checking if a reflog entry is valid.

This generally follows fsck's mental model that we will have
looked at and loaded a "struct object" for each object in
the repository. But it misses one case: if another object
_mentioned_ an object, but we didn't actually parse it or
verify that it exists, it will still have a struct.

It's not clear if this is a triggerable bug or not.
Certainly the later parts of the reachability check need to
be careful of this, and do so by checking the HAS_OBJ flag.
But both of these steps happen before we start traversing,
so probably we won't have followed any links yet. Still,
it's easy enough to be defensive here.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-01-17 14:24:33 -08:00
..
2016-09-19 13:47:19 -07:00
2016-11-22 13:55:20 -08:00
2016-10-10 14:03:51 -07:00
2016-09-22 13:42:18 -07:00
2016-02-26 13:37:16 -08:00
2016-09-29 15:42:18 -07:00
2016-09-21 15:15:24 -07:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:50 -07:00
2016-10-27 14:58:48 -07:00
2017-01-17 14:24:33 -08:00
2016-09-29 20:40:23 -07:00
2016-09-26 16:09:17 -07:00
2016-11-22 13:13:16 -08:00
2016-10-26 13:30:51 -07:00
2016-09-29 15:42:18 -07:00
2016-10-03 13:30:33 -07:00
2016-09-29 15:42:18 -07:00
2016-07-14 15:50:41 -07:00
2016-09-29 15:42:18 -07:00
2016-07-13 11:24:10 -07:00
2015-10-05 13:20:08 -07:00
2016-10-17 13:25:22 -07:00
2016-10-27 14:58:47 -07:00
2016-09-29 20:40:23 -07:00
2016-10-03 12:46:47 -07:00
2016-04-29 12:59:09 -07:00