Re: What's cooking in git.git (May 2018, #04; Wed, 30)

From: Duy Nguyen <pclouds@gmail.com>
Date: May 30, 2018, 16:27 UTC
Message-ID: <CACsJy8DW8e4rFWzzc4WxLRtK-WTAcG_BwFSxAya_fLfXOk9p8A@mail.gmail.com>
In-Reply-To: <xmqqy3g1d4xa.fsf@gitster-ct.c.googlers.com>

On Wed, May 30, 2018 at 8:38 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 20 quoted lines

> * sb/object-store-alloc (2018-05-16) 13 commits
>  - alloc: allow arbitrary repositories for alloc functions
>  - object: allow create_object to handle arbitrary repositories
>  - object: allow grow_object_hash to handle arbitrary repositories
>  - alloc: add repository argument to alloc_commit_index
>  - alloc: add repository argument to alloc_report
>  - alloc: add repository argument to alloc_object_node
>  - alloc: add repository argument to alloc_tag_node
>  - alloc: add repository argument to alloc_commit_node
>  - alloc: add repository argument to alloc_tree_node
>  - alloc: add repository argument to alloc_blob_node
>  - object: add repository argument to grow_object_hash
>  - object: add repository argument to create_object
>  - repository: introduce parsed objects field
>  (this branch is used by sb/object-store-grafts.)
>
>  The conversion to pass "the_repository" and then "a_repository"
>  throughout the object access API continues.
>
>  Is this ready for 'next'?

I think so. Stefan could remove the comment "/* TODO: what about commit->util? */" if he wants since nd/commit-util-to-slab is already in next. But this is really minor and does not need fixing to land on 'next'.

-- 
Duy