git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Stefan Beller <sbeller@google.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2018, #04; Wed, 30)
Date: Wed, 30 May 2018 18:27:27 +0200	[thread overview]
Message-ID: <CACsJy8DW8e4rFWzzc4WxLRtK-WTAcG_BwFSxAya_fLfXOk9p8A@mail.gmail.com> (raw)
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:
> * 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

  parent reply	other threads:[~2018-05-30 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  6:38 What's cooking in git.git (May 2018, #04; Wed, 30) Junio C Hamano
2018-05-30 16:09 ` Taylor Blau
2018-05-30 16:12   ` Taylor Blau
2018-06-11 20:04     ` Taylor Blau
2018-06-11 22:44       ` Junio C Hamano
2018-05-31 23:15   ` Junio C Hamano
2018-05-30 16:27 ` Duy Nguyen [this message]
2018-05-30 16:43   ` Stefan Beller
2018-05-31 23:58   ` 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=CACsJy8DW8e4rFWzzc4WxLRtK-WTAcG_BwFSxAya_fLfXOk9p8A@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sbeller@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).