Jeff King wrote
> Fundamentally the problem is
> that the --local transport is not safe from propagating corruption, and
> should not be used if that's a requirement.
I've read Jeff Mitchell's blog post, his update, relevant parts of the
git-clone(1) man page, and a decent chunk of this thread, an
Jonathan Nieder-2 wrote
> Is the "[transfer] fsckObjects" configuration on the host executing the
> clone set to true?
I hadn't been setting it at all, and according to git-config(1) it defaults
to false, so the answer is no. It looks like setting it might be a good
idea.
But I'm still somewhat
Junio C Hamano wrote
> If you use --local, that is equivalent to "cp -R". Your corruption
> in the source will faithfully be byte-for-byte copied to the
> destination. If you do not
> ...
> transport layer will notice
> object corruption.
> ...
> The difference between --mirror and no --mirror is
3 matches
Mail list logo
