Re: [PATCH 2/6] Accept object data in the fsck_object() function

On Thu, Aug 28, 2014 at 01:47:52PM -0700, Junio C Hamano wrote: > Johannes Schindelin writes: > > > When fsck'ing an incoming pack, we need to fsck objects that cannot be > > read via read_sha1_file() because they are not local yet (and might even > > be rejected if transfer.fsckobjects is set t

Re: [PATCH 2/6] Accept object data in the fsck_object() function

On Thu, Aug 28, 2014 at 04:46:42PM +0200, Johannes Schindelin wrote: > When fsck'ing an incoming pack, we need to fsck objects that cannot be > read via read_sha1_file() because they are not local yet (and might even > be rejected if transfer.fsckobjects is set to 'true'). > > For commits, there

Re: [PATCH 2/6] Accept object data in the fsck_object() function

Johannes Schindelin writes: > When fsck'ing an incoming pack, we need to fsck objects that cannot be > read via read_sha1_file() because they are not local yet (and might even > be rejected if transfer.fsckobjects is set to 'true'). > > For commits, there is a hack in place: we basically cache co

[PATCH 2/6] Accept object data in the fsck_object() function

When fsck'ing an incoming pack, we need to fsck objects that cannot be read via read_sha1_file() because they are not local yet (and might even be rejected if transfer.fsckobjects is set to 'true'). For commits, there is a hack in place: we basically cache commit objects' buffers anyway, but the s