From: Jeff Hostetler <git@jeffhostetler.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
Jeff Hostetler <jeffhost@microsoft.com>,
Jonathan Tan <jonathantanmy@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)
Date: Mon, 30 Oct 2017 15:54:14 -0400 [thread overview]
Message-ID: <f12353b6-cfed-722b-1386-d55700f21915@jeffhostetler.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1710301830210.6482@virtualbox>
On 10/30/2017 1:31 PM, Johannes Schindelin wrote:
> Hi Junio,
>
> On Mon, 30 Oct 2017, Junio C Hamano wrote:
>
>> * 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
>
Right. I posted a "part 1" of this last week and am currently
rerolling that. I should also have a followup "part 2" patch
series shortly.
https://public-inbox.org/git/20171024185332.57261-1-git@jeffhostetler.com/
I've been assuming that the jt/partial-clone-lazy-fetch is a
placeholder for our next combined patch series.
Jeff
next prev parent reply other threads:[~2017-10-30 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 6:19 What's cooking in git.git (Oct 2017, #07; Mon, 30) Junio C Hamano
2017-10-30 12:40 ` Ben Peart
2017-10-30 17:24 ` Johannes Schindelin
2017-10-30 17:28 ` Johannes Schindelin
2017-10-31 2:38 ` Junio C Hamano
2017-10-31 17:18 ` Johannes Schindelin
2017-10-30 17:31 ` Johannes Schindelin
2017-10-30 19:54 ` Jeff Hostetler [this message]
2017-10-31 2:40 ` Junio C Hamano
2017-10-31 13:14 ` Jeff Hostetler
2017-11-01 1:21 ` Junio C Hamano
2017-11-01 17:58 ` Jonathan Tan
2017-11-02 1:13 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f12353b6-cfed-722b-1386-d55700f21915@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=jonathantanmy@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://80x24.org/mirrors/git.git
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).