mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <>
To: Junio C Hamano <>
	Jeff Hostetler <>
Subject: Re: [PATCH v2] partial-clone: design doc
Date: Thu, 14 Dec 2017 16:02:38 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/14/2017 1:24 PM, Junio C Hamano wrote:
> Jeff Hostetler <> writes:
>> +- On the client these incomplete packfiles are marked as "promisor pacfiles"
> s/pacfiles/packfiles/
>> +  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?

good point.  i'll move this to the bottom and elaborate on the
problem rather than the solution.


  reply	other threads:[~2017-12-14 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 15:24 [PATCH v2] Partial clone design document Jeff Hostetler
2017-12-14 15:24 ` [PATCH v2] partial-clone: design doc Jeff Hostetler
2017-12-14 18:24   ` Junio C Hamano
2017-12-14 21:02     ` Jeff Hostetler [this message]
2017-12-14 18:27   ` Junio C Hamano

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).