Re: Allowing "/" in the name of a git remote is a strange choice

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 4, 2025, 14:18 UTC
Message-ID: <xmqqecuwavk3.fsf@gitster.g>
In-Reply-To: <aGdi6GRbI6Txm25Q@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 7 quoted lines

>> So it is not like we can just forbid '/' retroactively and expect no
>> repercussions, especially given that I hear there are more than a
>> few thousands of existing Git users in the world.
>
> We cannot just blanket-disallow this now, true. But shouldn't Git be
> able to detect this conflict, similar to how a user cannot have both
> refs/heads/branch and refs/heads/branch/nested?

Yup. Sorry but I should probably have not left it out, as that was way too obvious an improved "solution", compared to "just forbid '/', as I cannot imagine anybody using it".