From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jiang Xin <worldhello.net@gmail.com>
Subject: ab/object-file-api-updates (was: What's cooking in git.git (Feb 2022, #08; Mon, 28))
Date: Thu, 03 Mar 2022 17:11:46 +0100 [thread overview]
Message-ID: <220303.86v8wv2evg.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqmti9ssah.fsf@gitster.g>
On Tue, Mar 01 2022, Junio C Hamano wrote:
> * ab/object-file-api-updates (2022-02-25) 12 commits
> - object-file API: pass an enum to read_object_with_reference()
> - object-file.c: add a literal version of write_object_file_prepare()
> - object-file API: have hash_object_file() take "enum object_type"
> - object API: rename hash_object_file_literally() to write_*()
> - object-file API: split up and simplify check_object_signature()
> - object API users + docs: check <0, not !0 with check_object_signature()
> - object API docs: move check_object_signature() docs to cache.h
> - object API: correct "buf" v.s. "map" mismatch in *.c and *.h
> - object-file API: have write_object_file() take "enum object_type"
> - object-file API: add a format_object_header() function
> - object-file API: return "void", not "int" from hash_object_file()
> - object-file.c: split up declaration of unrelated variables
>
> Object-file API shuffling.
>
> Needs review.
> source: <cover-v3-00.12-00000000000-20220204T234435Z-avarab@gmail.com>
Jiang Xin (whose git-unpack-objects series at [1] depends on this) has
looked this over & acked it at [2].
1. https://lore.kernel.org/git/cover-v10-0.6-00000000000-20220204T135538Z-avarab@gmail.com/
2. https://lore.kernel.org/git/CANYiYbFZN=mvcxRT4Cf4Gzao89KR2UjMJXnJM63S2zAtbD32Jg@mail.gmail.com/
next prev parent reply other threads:[~2022-03-03 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 13:42 What's cooking in git.git (Feb 2022, #08; Mon, 28) Junio C Hamano
2022-03-01 14:26 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)) Derrick Stolee
2022-03-01 14:58 ` Patrick Steinhardt
2022-03-01 18:07 ` Junio C Hamano
2022-03-01 22:55 ` js/scalar-diagnose, was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28) Johannes Schindelin
2022-03-02 7:05 ` Junio C Hamano
2022-03-02 1:26 ` en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)) Elijah Newren
2022-03-07 16:31 ` Johannes Schindelin
2022-03-08 8:30 ` Elijah Newren
2022-03-09 11:46 ` Johannes Schindelin
2022-03-03 16:11 ` Ævar Arnfjörð Bjarmason [this message]
2022-03-03 22:23 ` ab/object-file-api-updates 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=220303.86v8wv2evg.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@gmail.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.
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.