Re: propagating repo corruption across clone

From: Duy Nguyen <pclouds@gmail.com>
Date: Mar 25, 2013, 15:31 UTC
Message-ID: <CACsJy8A0eOWEJ2aqPSLof_CodJM6BadFxQHy5Vb0kAwwTSTS3w@mail.gmail.com>
In-Reply-To: <20130325145644.GA16576@sigill.intra.peff.net>

On Mon, Mar 25, 2013 at 9:56 PM, Jeff King <peff@peff.net> wrote:

Show 14 quoted lines

> There are basically three levels of transport that can be used on a
> local machine:
>
>   1. Hard-linking (very fast, no redundancy).
>
>   2. Byte-for-byte copy (medium speed, makes a separate copy of the
>      data, but does not check the integrity of the original).
>
>   3. Regular git transport, creating a pack (slowest, but should include
>      redundancy checks).
>
> Using --no-hardlinks turns off (1), but leaves (2) as an option.  I
> think the documentation in "git clone" could use some improvement in
> that area.

Not only git-clone. How git-fetch and git-push verify the new pack should also be documented. I don't think many people outside the contributor circle know what is done (and maybe how) when data is received from outside.

-- 
Duy