From: Jeff King <peff@peff.net>
To: Ryne Everett <ryneeverett@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: Fsck configurations and cloning.
Date: Sun, 6 Mar 2016 11:00:23 -0500 [thread overview]
Message-ID: <20160306160022.GA20010@sigill.intra.peff.net> (raw)
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:
> > 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.
> > 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
prev parent reply other threads:[~2016-03-06 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 1:44 Fsck configurations and cloning Ryne Everett
2016-03-06 5:18 ` Jacob Keller
2016-03-06 15:31 ` Ryne Everett
2016-03-06 11:58 ` Jeff King
2016-03-06 15:38 ` Ryne Everett
2016-03-06 16:00 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160306160022.GA20010@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=ryneeverett@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).