From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #04)
Date: Tue, 13 Jan 2026 16:27:35 -0800 [thread overview]
Message-ID: <xmqq1pjthwco.fsf@gitster.g> (raw)
In-Reply-To: <xmqqjyxli89m.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 13 Jan 2026 12:10:13 -0800")
The following topics have been merged to 'next'.
> * ps/ref-consistency-checks (2026-01-12) 17 commits
>
> Update code paths that check data integrity around refs subsystem.
>
> Will merge to 'next".
> cf. <CAOLa=ZShPP3BPXa=YnC-vuX4zF=pUTFdUidZwOdna8bfVTNM9w@mail.gmail.com>
> source: <20260112-pks-refs-verify-fixes-v2-0-2e9e453bd6c3@pks.im>
> * cs/rebased-subtree-split (2026-01-09) 1 commit
>
> The split command in "git subtree" (in contrib/) has been taught to
> deal better with rebased history.
>
> Will merge to 'next'.
> source: <20260110011811.788219-1-ask+git@howdoi.land>
> * kt/http-backend-errors (2026-01-11) 1 commit
>
> Some error messages from the http transport layer lacked the
> terminating newline, which has been corrected.
>
> Will merge to 'next'.
> source: <20260112014508.17248-1-kj@kjtsanaktsidis.id.au>
> * ps/t1410-cleanup (2026-01-11) 1 commit
>
> Test clean-up.
>
> Will merge to 'next'.
> source: <20260111191525.17087-1-pushkarkumarsingh1970@gmail.com>
> * tb/macos-iconv-workarounds (2026-01-11) 2 commits
>
> The iconv library on macOS fails to correctly handle stateful
> ISO/IEC 2022 encoded strings. Work it around instead of replacing
> it wholesale from homebrew.
>
> Will merge to 'next'.
> source: <20260111195151.716191-1-tboegi@web.de>
next prev parent reply other threads:[~2026-01-14 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:10 What's cooking in git.git (Jan 2026, #04) Junio C Hamano
2026-01-14 0:27 ` Junio C Hamano [this message]
2026-01-14 5:20 ` Patrick Steinhardt
2026-01-14 14:26 ` Junio C Hamano
2026-01-14 17:35 ` Patrick Steinhardt
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=xmqq1pjthwco.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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