Re: Allowing "/" in the name of a git remote is a strange choice
- From
Lidong Yan <yldhome2d2@gmail.com>
- Date
- Jul 4, 2025, 08:10 UTC
- Message-ID
- <10608B81-587A-4DED-ADC6-8F57B0B67E39@gmail.com>
- In-Reply-To
- <aGdi6GRbI6Txm25Q@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
> 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?
Perhaps we should forbid having two remotes where one is the directory base (i.e., a prefix) of the other.