From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2026, #01)
Date: Thu, 2 Apr 2026 08:57:00 +0200 [thread overview]
Message-ID: <ac4TPLj3tItmR_P-@pks.im> (raw)
In-Reply-To: <xmqqikaatfhp.fsf@gitster.g>
On Wed, Apr 01, 2026 at 04:42:10PM -0700, Junio C Hamano wrote:
> * ps/reftable-portability (2026-03-31) 6 commits
> - reftable: introduce "reftable-system.h" header
> - reftable/system: add abstraction to mmap files
> - reftable/system: add abstraction to retrieve time in milliseconds
> - reftable/fsck: use REFTABLE_UNUSED instead of UNUSED
> - reftable/stack: don't call fsync(3p) unless provided
> - reftable/system: provide `REFTABLE_INLINE()` macro
>
> Update reftable library part with what is used in libgit2 to improve
> portability to different target codebases and platforms.
>
> Will merge to 'next'?
> source: <20260331-pks-reftable-portability-fixes-v1-0-46bfae55c68c@pks.im>
Not yet, please, as I plan to send a second version of this series
today.
> * ps/odb-cleanup (2026-03-31) 7 commits
> - odb: drop unneeded headers and forward decls
> - odb: rename `odb_has_object()` flags
> - odb: use enum for `odb_write_object` flags
> - odb: rename `odb_write_object()` flags
> - treewide: use enum for `odb_for_each_object()` flags
> - CodingGuidelines: document our style for flags
> - Merge branch 'ps/odb-generic-object-name-handling' into ps/odb-cleanup
> (this branch uses ps/odb-generic-object-name-handling.)
>
> Various code clean-up around odb subsystem.
>
> Will merge to 'next'?
> source: <20260401-pks-odb-cleanups-v1-0-89adba9ada68@pks.im>
No concerns here. It's a rather boring and unexciting patch series that
doesn't do much anyway, other than following through with what we've
discussed over the last couple weeks with regards to flags.
Thanks!
Patrick
next prev parent reply other threads:[~2026-04-02 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 23:42 What's cooking in git.git (Apr 2026, #01) Junio C Hamano
2026-04-02 6:57 ` Patrick Steinhardt [this message]
2026-04-09 19:54 ` René Scharfe
2026-04-09 20:09 ` 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=ac4TPLj3tItmR_P-@pks.im \
--to=ps@pks.im \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox