Hi,
Ben Peart wrote:
> We've discussed a couple of different possible solutions, each of
> which have different tradeoffs. Let me try to summarize here and
> perhaps suggest some other possibilities:
Thanks for this. Some comments below.
> Promised list
> -
> This provides an exte
On 8/7/2017 3:41 PM, Junio C Hamano wrote:
Ben Peart writes:
My concern with this proposal is the combination of 1) writing a new
pack file for every git command that ends up bringing down a missing
object and 2) gc not compressing those pack files into a single pack
file.
Your noticing th
On 8/7/2017 3:21 PM, Jonathan Nieder wrote:
Hi,
Ben Peart wrote:
On Fri, 04 Aug 2017 15:51:08 -0700
Junio C Hamano wrote:
Jonathan Tan writes:
"Imported" objects must be in a packfile that has a ".remote"
file with arbitrary text (similar to the ".keep" file). They come from
clones, fet
On Mon, 7 Aug 2017 15:12:11 -0400
Ben Peart wrote:
> I missed the offline discussion and so am trying to piece together what
> this latest design is trying to do. Please let me know if I'm not
> understanding something correctly.
>
> From what I can tell, objects are going to be segmented in
Ben Peart writes:
> My concern with this proposal is the combination of 1) writing a new
> pack file for every git command that ends up bringing down a missing
> object and 2) gc not compressing those pack files into a single pack
> file.
Your noticing these is a sign that you read the outline o
Hi,
Ben Peart wrote:
>> On Fri, 04 Aug 2017 15:51:08 -0700
>> Junio C Hamano wrote:
>>> Jonathan Tan writes:
"Imported" objects must be in a packfile that has a ".remote"
file with arbitrary text (similar to the ".keep" file). They come from
clones, fetches, and the object loader
On 8/4/2017 8:21 PM, Jonathan Tan wrote:
On Fri, 04 Aug 2017 15:51:08 -0700
Junio C Hamano wrote:
Jonathan Tan writes:
"Imported" objects must be in a packfile that has a ".remote"
file with arbitrary text (similar to the ".keep" file). They come from
clones, fetches, and the object loade
On Fri, 04 Aug 2017 15:51:08 -0700
Junio C Hamano wrote:
> Jonathan Tan writes:
>
> > "Imported" objects must be in a packfile that has a ".remote"
> > file with arbitrary text (similar to the ".keep" file). They come from
> > clones, fetches, and the object loader (see below).
> > ...
> > A "h
Jonathan Tan writes:
> "Imported" objects must be in a packfile that has a ".remote"
> file with arbitrary text (similar to the ".keep" file). They come from
> clones, fetches, and the object loader (see below).
> ...
> A "homegrown" object is valid if each object it references:
> 1. is a "homeg
After some discussion in [1] (in particular, about preserving the
functionality of the connectivity check as much as possible) and some
in-office discussion, here's an updated design.
Overview
This is an update of the design in [1].
The main difference between this and other related wor
10 matches
Mail list logo