Re: [PATCH 00/10] RFC Partial Clone and Fetch

From: ankostis <ankostis@gmail.com>
Date: Mar 22, 2017, 15:16 UTC
Message-ID: <CA+dhYEWo3v+ns0zt_hWu-7i-=E0g_tFaXYcv7Q0j2ozx1SCVmQ@mail.gmail.com>
In-Reply-To: <1488999039-37631-1-git-send-email-git@jeffhostetler.com>

Dear Jeff

I read most of the valuable references you provided but could not find something along the lines describing inline.

On 8 March 2017 at 19:50,  <git@jeffhostetler.com> wrote:

Show 11 quoted lines

> From: Jeff Hostetler <jeffhost@microsoft.com>
>
>
> [RFC] Partial Clone and Fetch
> =============================
>
> This is a WIP RFC for a partial clone and fetch feature wherein the client
> can request that the server omit various blobs from the packfile during
> clone and fetch.  Clients can later request omitted blobs (either from a
> modified upload-pack-like request to the server or via a completely
> independent mechanism).

Is it foreseen the server to *decide* with partial objects to serve And the cloning-client still to work ok?

My case in mind is storing confidential files in Git (server) that I want to publicize them to partial-cloning clients, for non-repudiation, by sending out trees and commits alone (or any non-sensitive blobs).

A possible UI would be to rely on a `.gitattributes` to specify which objects are to be upheld.

Apologies if I'm intruding with an unrelated feature requests.
  Kostis