From: Toon Claes <toon@iotcl•com>
To: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #02)
Date: Wed, 07 Jan 2026 21:15:37 +0100 [thread overview]
Message-ID: <87wm1tnpqu.fsf@iotcl.com> (raw)
In-Reply-To: <xmqqbjj8koe8.fsf@gitster.g>
Junio C Hamano <gitster@pobox•com> writes:
> * sb/bundle-uri-without-uri (2025-12-19) 1 commit
> (merged to 'next' on 2026-01-05 at 62d0a58199)
> + bundle-uri: validate that bundle entries have a uri
>
> Diagnose invalid bundle-URI that lack the URI entry, instead of
> crashing.
>
> Will merge to 'master'.
> source: <pull.2134.v2.git.git.1766160106521.gitgitgadget@gmail•com>
Cool! I had this one in my backlog to look into, and now I did. Looks
good to me, as a matter of fact, I had a similar patch somewhere in my
local worktree.
--
Cheers,
Toon
prev parent reply other threads:[~2026-01-07 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:36 What's cooking in git.git (Jan 2026, #02) Junio C Hamano
2026-01-07 15:13 ` Toon Claes
2026-01-07 20:15 ` Toon Claes [this message]
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=87wm1tnpqu.fsf@iotcl.com \
--to=toon@iotcl$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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