git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] partial-clone: design doc

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 14, 2017, 18:24 UTC
Message-ID
<xmqq1sjxuq0a.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20171214152404.35708-2-git@jeffhostetler.com>
Jeff Hostetler <git@jeffhostetler.com> writes:
> +- On the client these incomplete packfiles are marked as "promisor pacfiles"
s/pacfiles/packfiles/
Show 6 quoted lines
> +  These "promisor packfiles" consist of a "<name>.promisor" file with
> +  arbitrary contents (like the "<name>.keep" files), in addition to
> +  their "<name>.pack" and "<name>.idx" files.
> +
> +  In the future, this ability may be extended to loose objects in case
> +  a promisor packfile is accidentally unpacked.
Hmph.

Because we cannot assume that such an "accidental" unpacking would do anything extra to help us tell the loose objects created out of a promisor pack from other loose objects, you would end up making any and all loose objects to serve as if they came from a promisor remote? I am not sure if that makes much sense.

Do we really need to write this "in the future" down, before we have thought things through enough to specify the design at a bit more detailed level?

Previous: Jeff HostetlerNext: Jeff Hostetler
Message 3 of 5 in “Partial clone design document”
  1. Partial clone design documentJeff Hostetler, Dec 14, 2017
  2. partial-clone: design docJeff Hostetler, Dec 14, 2017
  3. Junio C HamanoDec 14, 2017
  4. Jeff HostetlerDec 14, 2017
  5. Junio C HamanoDec 14, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.