Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 30, 2017, 17:31 UTC
Message-ID: <alpine.DEB.2.21.1.1710301830210.6482@virtualbox>
In-Reply-To: <xmqqr2tl40pl.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Mon, 30 Oct 2017, Junio C Hamano wrote:

Show 26 quoted lines

> * jt/partial-clone-lazy-fetch (2017-10-02) 18 commits
>  - fetch-pack: restore save_commit_buffer after use
>  - unpack-trees: batch fetching of missing blobs
>  - clone: configure blobmaxbytes in created repos
>  - clone: support excluding large blobs
>  - fetch: support excluding large blobs
>  - fetch: refactor calculation of remote list
>  - fetch-pack: support excluding large blobs
>  - pack-objects: support --blob-max-bytes
>  - pack-objects: rename want_.* to ignore_.*
>  - gc: do not repack promisor packfiles
>  - rev-list: support termination at promisor objects
>  - sha1_file: support lazily fetching missing objects
>  - introduce fetch-object: fetch one promisor object
>  - index-pack: refactor writing of .keep files
>  - fsck: support promisor objects as CLI argument
>  - fsck: support referenced promisor objects
>  - fsck: support refs pointing to promisor objects
>  - fsck: introduce partialclone extension
> 
>  A journey for "git clone" and "git fetch" to become "lazier" by
>  depending more on its remote repository---this is the beginning of
>  it.
> 
>  Expecting a reroll.
>  cf. <CAGf8dgLu-TeK8KbHv-U+18O+L2TxKcGv5vFFHy38J6a_YXRfew@mail.gmail.com>

It was my understanding that Jeff's heavy-lifting produced a shorter, initial patch series with parts of this, that was already reviewed internally by Jonathan.

Am I mistaken?

Ciao, Dscho