From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Mar 2025, #06; Fri, 21)
Date: Mon, 24 Mar 2025 11:19:58 +0100 [thread overview]
Message-ID: <Z-ExzkjgAor2JQ2r@pks.im> (raw)
In-Reply-To: <xmqqiko2tguo.fsf@gitster.g>
On Fri, Mar 21, 2025 at 10:48:31AM -0700, Junio C Hamano wrote:
> * ps/reftable-sans-compat-util (2025-02-18) 18 commits
> - Makefile: skip reftable library for Coccinelle
> - reftable: decouple from Git codebase by pulling in "compat/posix.h"
> - git-compat-util.h: split out POSIX-emulating bits
> - compat/mingw: split out POSIX-related bits
> - reftable/basics: introduce `REFTABLE_UNUSED` annotation
> - reftable/basics: stop using `SWAP()` macro
> - reftable/stack: stop using `sleep_millisec()`
> - reftable/system: introduce `reftable_rand()`
> - reftable/reader: stop using `ARRAY_SIZE()` macro
> - reftable/basics: provide wrappers for big endian conversion
> - reftable/basics: stop using `st_mult()` in array allocators
> - reftable: stop using `BUG()` in trivial cases
> - reftable/record: don't `BUG()` in `reftable_record_cmp()`
> - reftable/record: stop using `BUG()` in `reftable_record_init()`
> - reftable/record: stop using `COPY_ARRAY()`
> - reftable/blocksource: stop using `xmmap()`
> - reftable/stack: stop using `write_in_full()`
> - reftable/stack: stop using `read_in_full()`
> (this branch is used by ps/reftable-windows-unlink-fix.)
>
> Make the code in reftable library less reliant on the service
> routines it used to borrow from Git proper, to make it easier to
> use by external users of the library.
>
> Waiting for Acks, especially for Windows bits?
> source: <20250218-pks-reftable-drop-git-compat-util-v6-0-8c1f39fb4c02@pks.im>
Johannes mentioned [1] that we can move forward with this topic, so I
think it can be merged now. Thanks!
Patrick
[1]: https://github.com/gitgitgadget/git/pull/1874#issuecomment-2740342672
prev parent reply other threads:[~2025-03-24 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 17:48 What's cooking in git.git (Mar 2025, #06; Fri, 21) Junio C Hamano
2025-03-21 21:10 ` Karthik Nayak
2025-03-24 10:19 ` Patrick Steinhardt [this message]
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=Z-ExzkjgAor2JQ2r@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).