All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Han Xin <chiyutianyi@gmail.com>
Subject: Re: hx/unpack-streaming
Date: Thu, 23 Jun 2022 15:08:35 -0700	[thread overview]
Message-ID: <xmqqwnd7xcbg.fsf@gitster.g> (raw)
In-Reply-To: <220623.86o7yjk5l2.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Thu, 23 Jun 2022 12:59:11 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Wed, Jun 22 2022, Junio C Hamano wrote:
>
>> * hx/unpack-streaming (2022-06-13) 6 commits
>>  - unpack-objects: use stream_loose_object() to unpack large objects
>>  - core doc: modernize core.bigFileThreshold documentation
>>  - object-file.c: add "stream_loose_object()" to handle large object
>>  - object-file.c: factor out deflate part of write_loose_object()
>>  - object-file.c: refactor write_loose_object() to several steps
>>  - unpack-objects: low memory footprint for get_data() in dry_run mode
>>
>>  Allow large objects read from a packstream to be streamed into a
>>  loose object file straight, without having to keep it in-core as a
>>  whole.
>>
>>  Will merge to 'next'?
>>  source: <cover.1654914555.git.chiyutianyi@gmail.com>
>
> I've thoroughly reviewed this topic both now & in the past, and I think
> it's ready to be merged down.

I was involved in reviewing its earlier rounds but didn't read the
last round too carefully.  I'll give it another read-over before
merging it down.

Thanks, all.

  reply	other threads:[~2022-06-23 22:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 19:32 What's cooking in git.git (Jun 2022, #07; Wed, 22) Junio C Hamano
2022-06-22 21:16 ` en/merge-tree (Was: Re: What's cooking in git.git (Jun 2022, #07; Wed, 22)) Elijah Newren
2022-06-22 23:13   ` en/merge-tree Junio C Hamano
2022-06-23 10:02   ` en/merge-tree (Was: Re: What's cooking in git.git (Jun 2022, #07; Wed, 22)) Johannes Schindelin
2022-06-23 10:55 ` ab/test-without-templates (was: " Ævar Arnfjörð Bjarmason
2022-06-23 22:12   ` ab/test-without-templates Junio C Hamano
2022-06-27 12:29     ` ab/test-without-templates Ævar Arnfjörð Bjarmason
2022-06-27 16:11       ` ab/test-without-templates Junio C Hamano
2022-06-27 18:23         ` ab/test-without-templates Ævar Arnfjörð Bjarmason
2022-06-23 10:59 ` hx/unpack-streaming (was: What's cooking in git.git (Jun 2022, #07; Wed, 22)) Ævar Arnfjörð Bjarmason
2022-06-23 22:08   ` Junio C Hamano [this message]
2022-06-24  3:12 ` gc/submodule-update (was " Glen Choo
2022-06-24 15:35   ` 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

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

  git send-email \
    --in-reply-to=xmqqwnd7xcbg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=chiyutianyi@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.