git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2024, #09; Fri, 18)
Date: Mon, 21 Oct 2024 14:22:48 +0200	[thread overview]
Message-ID: <ZxZHmIJXLBvzoe3D@pks.im> (raw)
In-Reply-To: <ZxLI06smvMuf/cT2@nand.local>

On Fri, Oct 18, 2024 at 04:45:07PM -0400, Taylor Blau wrote:
> * ps/ref-filter-sort (2024-10-17) 1 commit
>  - ref-filter: format iteratively with lexicographic refname sorting
> 
>  Teaches the ref-filter machinery to recognize and avoid cases where
>  sorting would be redundant.
> 
>  Will merge to 'next'?
>  source: <e0daa6a2eac97c2b18a53399b7c124fc8d3d238d.1729141657.git.ps@pks.im>

I think v3 should be ready to go.

[snip]
> * ps/cmake-clar (2024-10-15) 3 commits
>  - cmake: set up proper dependencies for generated clar headers
>  - cmake: fix compilation of clar-based unit tests
>  - Makefile: extract script to generate clar declarations
> 
>  Buildfix for unit tests when using CMake.
> 
>  source: <cover.1728985514.git.ps@pks.im>

This one can be dropped, as I've merged it into ps/upgrade-clar in v2
now.

> * ps/platform-compat-fixes (2024-10-16) 10 commits
>  - http: fix build error on FreeBSD
>  - builtin/credential-cache: fix missing parameter for stub function
>  - t7300: work around platform-specific behaviour with long paths on MinGW
>  - t5500, t5601: skip tests which exercise paths with '[::1]' on Cygwin
>  - t3404: work around platform-specific behaviour on macOS 10.15
>  - t1401: make invocation of tar(1) work with Win32-provided one
>  - t/lib-gpg: fix setup of GNUPGHOME in MinGW
>  - t/lib-gitweb: test against the build version of gitweb
>  - t/test-lib: wire up NO_ICONV prerequisite
>  - t/test-lib: fix quoting of TEST_RESULTS_SAN_FILE
> 
>  Various platform compatibility fixes split out of the larger effort
>  to use Meson as the primary build tool.
> 
>  Will merge to 'next'?
>  source: <cover.1729060405.git.ps@pks.im>
> 
> * ps/reftable-strbuf (2024-10-17) 10 commits
>  - reftable: handle trivial `reftable_buf` errors
>  - reftable/stack: adapt `stack_filename()` to handle allocation failures
>  - reftable/record: adapt `reftable_record_key()` to handle allocation failures
>  - reftable/stack: adapt `format_name()` to handle allocation failures
>  - t/unit-tests: check for `reftable_buf` allocation errors
>  - reftable/blocksource: adapt interface name
>  - reftable: convert from `strbuf` to `reftable_buf`
>  - reftable/basics: provide new `reftable_buf` interface
>  - reftable: stop using `strbuf_addf()`
>  - reftable: stop using `strbuf_addbuf()`
> 
>  Implements a new reftable-specific strbuf replacement to reduce
>  reftable's dependency on Git-specific data structures.
> 
>  Will merge to 'next'?
>  source: <cover.1729140565.git.ps@pks.im>

These two are ready to go from my point of view, as well.

Patrick

  reply	other threads:[~2024-10-21 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 20:45 What's cooking in git.git (Oct 2024, #09; Fri, 18) Taylor Blau
2024-10-21 12:22 ` Patrick Steinhardt [this message]
2024-10-21 20:48   ` Taylor Blau

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=ZxZHmIJXLBvzoe3D@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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).