From: Dragan Simic Date: Sat, 06 Apr 2024 08:37:09 GMT Subject: Re: What's cooking in git.git (Apr 2024, #03; Fri, 5) Message-ID: In-Reply-To: On 2024-04-06 07:03, Junio C Hamano wrote: > Dragan Simic 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: >> >> 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. Ah, sorry, I wasn't precise enough, please let me explain. When I wrote "prefix", I had its use by humans in mind, e.g. for searching the "what's cooking" emails by hand, to see the statuses of one's patches. I mean, that's what I do -- by searching for "ds/", I can easily find the statuses of my patches in "what's cooking" emails. Does that make sense?