Jeff King 5afc4b1dc6 fsck: only provide oid/type in fsck_error callback
None of the callbacks actually care about having a "struct object";
they're happy with just the oid and type information. So let's give
ourselves more flexibility to avoid having a "struct object" by just
passing the broken-down fields.

Note that the callback already takes a "type" field for the fsck message
type. We'll rename that to "msg_type" (and use "object_type" for the
object type) to make the distinction explicit.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-10-28 14:05:18 +09:00
..
2019-10-15 13:47:59 +09:00
2019-10-11 14:24:48 +09:00
2019-09-18 11:50:09 -07:00
2019-10-11 14:24:48 +09:00
2019-01-29 12:47:54 -08:00
2019-10-15 13:48:02 +09:00
2019-04-25 16:41:12 +09:00
2019-10-15 13:48:02 +09:00
2019-10-15 13:48:03 +09:00
2018-10-19 13:34:02 +09:00
2019-09-18 11:50:09 -07:00
2019-09-30 13:19:32 +09:00
2019-10-07 11:32:53 +09:00
2019-05-13 14:22:54 +09:00
2019-08-19 13:05:58 -07:00
2019-10-15 13:48:03 +09:00
2019-10-11 14:24:46 +09:00
2019-10-11 14:24:46 +09:00
2019-07-19 11:30:21 -07:00
2019-10-11 14:24:48 +09:00
2019-06-19 08:19:21 -07:00
2019-10-11 14:24:48 +09:00