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 (Feb 2025, #09; Fri, 28)
Date: Tue, 4 Mar 2025 07:31:09 +0100 [thread overview]
Message-ID: <Z8aeLc-xelujEjTE@pks.im> (raw)
In-Reply-To: <xmqq7c591sus.fsf@gitster.g>
On Fri, Feb 28, 2025 at 04:45:31PM -0800, 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, did the new version of this patch series make your life any
easier? As far as I can see the conflicts in your "shears/seen" branch
seem to have been fixed, and the failing pipeline seems to be due to
other issues. If so, we would be able to move ahead with this patch
series and the dependent fix for Windows below.
> * ps/reftable-windows-unlink-fix (2025-02-18) 2 commits
> - reftable: ignore file-in-use errors when unlink(3p) fails on Windows
> - Merge branch 'ps/reftable-sans-compat-util' into ps/reftable-windows-unlink-fix
> (this branch uses ps/reftable-sans-compat-util.)
Thanks!
Patrick
next prev parent reply other threads:[~2025-03-04 6:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 0:45 What's cooking in git.git (Feb 2025, #09; Fri, 28) Junio C Hamano
2025-03-03 15:24 ` shejialuo
2025-03-03 17:03 ` Junio C Hamano
2025-03-04 6:27 ` Patrick Steinhardt
2025-03-04 12:25 ` shejialuo
2025-03-04 15:30 ` Junio C Hamano
2025-03-07 10:48 ` Karthik Nayak
2025-03-04 6:31 ` Patrick Steinhardt [this message]
2025-03-04 7:02 ` ps/reftable-sans-compat-util, was " Johannes Schindelin
2025-03-04 7:40 ` Johannes Schindelin
2025-03-04 9:46 ` Patrick Steinhardt
2025-03-04 10:06 ` Patrick Steinhardt
2025-03-26 16:57 ` Johannes Schindelin
2025-03-27 15:28 ` Junio C Hamano
2025-03-28 5:36 ` Patrick Steinhardt
2025-03-28 15:31 ` Johannes Schindelin
2025-03-30 0:56 ` Junio C Hamano
2025-03-29 23:56 ` 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=Z8aeLc-xelujEjTE@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/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).