From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2024, #03; Fri, 5)
Date: Fri, 05 Apr 2024 22:03:46 -0700 [thread overview]
Message-ID: <xmqqr0fjnkul.fsf@gitster.g> (raw)
In-Reply-To: <36f7e1b7122b0bdeb2e8b70f69abd331@manjaro.org> (Dragan Simic's message of "Sat, 06 Apr 2024 03:11:14 +0200")
Dragan Simic <dsimic@manjaro.org> writes:
>> * ds/fetch-config-parse-microfix (2024-04-05) 1 commit
>> - fetch: return when parsing submodule.recurse
>> A config parser callback function fell through instead of returning
>> after recognising and processing a variable, wasting cycles, which
>> has been corrected.
>> Will merge to 'next'.
>> source: <pull.1709.git.1712285542303.gitgitgadget@gmail.com>
>
> Isn't this an example of a prefix collision, i.e. "ds/" points
> to two different contributors?
"ls .git/objects/" would tell you that no object is important enough
to squat on a single "prefix" and exclude others, and two objects in
00/ hierarchy are by no means closer together than an object in 00/
hierarchy and another object in 01/ hiearchy. The idea to use the
fan-out in the ref namespace is pretty much the same.
next prev parent reply other threads:[~2024-04-06 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 19:13 What's cooking in git.git (Apr 2024, #03; Fri, 5) Junio C Hamano
2024-04-05 20:06 ` Jeff King
2024-04-06 1:11 ` Dragan Simic
2024-04-06 5:03 ` Junio C Hamano [this message]
2024-04-06 8:37 ` Dragan Simic
2024-04-06 16:55 ` Junio C Hamano
2024-04-06 17:01 ` Dragan Simic
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=xmqqr0fjnkul.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dsimic@manjaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.