Re: Fsck configurations and cloning.

From: Jeff King <peff@peff.net>
Date: Mar 6, 2016, 16:00 UTC
Message-ID: <20160306160022.GA20010@sigill.intra.peff.net>
In-Reply-To: <CAGbFckYi1-b1NTaiQ8q1Ny_2+2rZFGMz+R-xgfRo1u5P-LKDwg@mail.gmail.com>

On Sun, Mar 06, 2016 at 10:38:15AM -0500, Ryne Everett wrote:

Show 12 quoted lines

> > I think there are two problems here.
> >
> > The first is that fsck.skiplist takes a filename that contains a list of
> > sha1s, not the sha1s themselves. So it would be more like:
> >
> >   echo 5e6ecdad9f69b1ff789a17733b8edc6fd7091bd8 >skiplist
> >   git -c fsck.skiplist="$(pwd)/skiplist" clone ...
> 
> I think I got this one right. Note the use of `cat` in my original post:
> 
>   $ cat $(git config --get fsck.skiplist)
>     5e6ecdad9f69b1ff789a17733b8edc6fd7091bd8

Oh, indeed, I missed that completely.

Show 5 quoted lines

> > The second is is that only "fsck" and "receive-pack" seem to have
> > learned about skiplist and other per-error config. There is no matching
> > fetch.fsck.* config to cover fetches.
> 
> Ah, well that sounds like the answer -- my original assumption was wrong.

Yeah. I was kind of surprised to find this was the case, given that we _do_ have fetch.fsckObjects.

-Peff