git/list[1] front-page[2] threads[3] people[4] search[5] about
 

ps/reftable-sans-compat-util, was Re: What's cooking in git.git (Feb 2025, #09; Fri, 28)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 4, 2025, 07:02 UTC
Message-ID
<0c808b85-d97c-ecd3-0b1d-fba546a1124b@gmx.de>
In-Reply-To
<Z8aeLc-xelujEjTE@pks.im>
Hi Patrick,
On Tue, 4 Mar 2025, Patrick Steinhardt wrote:
Show 34 quoted lines
> 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.

Honestly, I cannot say whether it made my life any easier. As you can see from https://github.com/git-for-windows/git/actions/workflows/main.yml?query=branch%3Ashears%2Fseen, the `shears/seen` branch failed to update automatically since I updated it manually last Thursday. According to https://github.com/git/git/activity?ref=seen, there have been 5 updates that were hence missed.

I'll try to update the `shears/seen` branch now, but I'll time-box it to half an hour because I really planned on taking care of other issues.

Ciao, Johannes

Previous: Patrick SteinhardtNext: Johannes Schindelin
Message 9 of 18 in “What's cooking in git.git (Feb 2025, #09; Fri, 28)”
  1. Junio C HamanoMar 1, 2025
  2. shejialuoMar 3, 2025
  3. Junio C HamanoMar 3, 2025
  4. Patrick SteinhardtMar 4, 2025
  5. shejialuoMar 4, 2025
  6. Junio C HamanoMar 4, 2025
  7. Karthik NayakMar 7, 2025
  8. Patrick SteinhardtMar 4, 2025
  9. ps/reftable-sans-compat-util, was Re: What's cooking in git.git (Feb 2025, #09; Fri, 28)Johannes Schindelin, Mar 4, 2025
  10. Johannes SchindelinMar 4, 2025
  11. Patrick SteinhardtMar 4, 2025
  12. Patrick SteinhardtMar 4, 2025
  13. Johannes SchindelinMar 26, 2025
  14. Junio C HamanoMar 27, 2025
  15. Patrick SteinhardtMar 28, 2025
  16. Johannes SchindelinMar 28, 2025
  17. Junio C HamanoMar 30, 2025
  18. Junio C HamanoMar 29, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.