git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/refs-errno-cleanup + hn/reftable (was: What's cooking in git.git (Nov 2021, #04; Sun, 14))
Date: Mon, 15 Nov 2021 20:37:57 +0100	[thread overview]
Message-ID: <211115.86sfvxqkbb.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqv90tfhh2.fsf@gitster.g>


On Mon, Nov 15 2021, Junio C Hamano wrote:

> * ab/refs-errno-cleanup (2021-10-16) 21 commits
>   (merged to 'next' on 2021-10-29 at 3f57147176)
>  + refs API: post-migration API renaming [2/2]
>  + refs API: post-migration API renaming [1/2]
>  + refs API: don't expose "errno" in run_transaction_hook()
>  + refs API: make expand_ref() & repo_dwim_log() not set errno
>  + refs API: make resolve_ref_unsafe() not set errno
>  + refs API: make refs_ref_exists() not set errno
>  + refs API: make refs_resolve_refdup() not set errno
>  + refs tests: ignore ignore errno in test-ref-store helper
>  + refs API: ignore errno in worktree.c's find_shared_symref()
>  + refs API: ignore errno in worktree.c's add_head_info()
>  + refs API: make files_copy_or_rename_ref() et al not set errno
>  + refs API: make loose_fill_ref_dir() not set errno
>  + refs API: make resolve_gitlink_ref() not set errno
>  + refs API: remove refs_read_ref_full() wrapper
>  + refs/files: remove "name exist?" check in lock_ref_oid_basic()
>  + reflog tests: add --updateref tests
>  + refs API: make refs_rename_ref_available() static
>  + refs API: make parse_loose_ref_contents() not set errno
>  + refs API: make refs_read_raw_ref() not set errno
>  + refs API: add a version of refs_resolve_ref_unsafe() with "errno"
>  + branch tests: test for errno propagating on failing read
>
> The "remainder" of hn/refs-errno-cleanup topic.
>
> Will cook in 'next'.
>
> [...]
>
> * hn/reftable (2021-10-08) 19 commits
>  - Add "test-tool dump-reftable" command.
>  - reftable: add dump utility
>  - reftable: implement stack, a mutable database of reftable files.
>  - reftable: implement refname validation
>  - reftable: add merged table view
>  - reftable: add a heap-based priority queue for reftable records
>  - reftable: reftable file level tests
>  - reftable: read reftable files
>  - reftable: generic interface to tables
>  - reftable: write reftable files
>  - reftable: a generic binary tree implementation
>  - reftable: reading/writing blocks
>  - Provide zlib's uncompress2 from compat/zlib-compat.c
>  - reftable: (de)serialization for the polymorphic record type.
>  - reftable: add blocksource, an abstraction for random access reads
>  - reftable: utility functions
>  - reftable: add error related functionality
>  - reftable: add LICENSE
>  - hash.h: provide constants for the hash IDs
>
>  The "reftable" backend for the refs API, without integrating into
>  the refs subsystem.
>
>  Will merge to 'next'?

I think hn/reftable is very much ready for "next", and it would be good
to get a strong start at the greater "reftable" topic this cycle, which
ab/refs-errno-cleanup is also a part of.

As noted in a recent thread[1] I've got pending patches on top of it
that go further in closing the gap between hn/reftable and eventual full
in-tree integration.

1. https://lore.kernel.org/git/211111.86k0hevjhs.gmgdl@evledraar.gmail.com/

  parent reply	other threads:[~2021-11-16  0:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 17:37 What's cooking in git.git (Nov 2021, #04; Sun, 14) Junio C Hamano
2021-11-15 19:30 ` ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #04; Sun, 14)) Ævar Arnfjörð Bjarmason
2021-11-15 22:16   ` Elijah Newren
2021-11-15 19:35 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2021-11-15 19:37 ` Ævar Arnfjörð Bjarmason [this message]
2021-11-15 20:00 ` What's cooking in git.git (Nov 2021, #04; Sun, 14) Fabian Stelzer

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=211115.86sfvxqkbb.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).