From: Karthik Nayak <karthik.188@gmail.com>
Date: Fri, 30 Jan 2026 12:06:11 GMT
Subject: Re: What's cooking in git.git (Jan 2026, #10)
Message-ID: <CAOLa=ZS8zbWoetOrfj9wXTQ78Ns663S6vCADabzTV26uEQsKLQ@mail.gmail.com>
In-Reply-To: <xmqqwm107za7.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:


> * kn/ref-batch-output-error-reporting-fix (2026-01-25) 6 commits
>  - fetch: delay user information post committing of transaction
>  - receive-pack: utilize rejected ref error details
>  - fetch: utilize rejected ref error details
>  - update-ref: utilize rejected error details if available
>  - refs: add rejection detail to the callback function
>  - refs: skip to next ref when current ref is rejected
>
>  A handful of code paths that started using batched ref update API
>  (after Git 2.51 or so) lost detailed error output, which have been
>  corrected.
>
>  Will merge to 'next'?
>  source: <20260125-633-regression-lost-diagnostic-message-when-pushing-non-commit-objects-to-refs-heads-v5-0-d58f3a9edf98@gmail.com>
>

I think we should be okay to merge this down. I've addressed all
reviews!

Thanks