Re: Creation of a branch named that has a directory prefix equal to the name of another branch fail.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 24, 2020, 20:36 UTC
- Message-ID
- <xmqqzh7ok5vu.fsf@gitster.c.googlers.com>
- In-Reply-To
- <DM5PR1801MB20762477763E6298C7FE6315F0770@DM5PR1801MB2076.namprd18.prod.outlook.com>
Tommaso Ercole <Tommaso.Ercole@qlik.com> writes:
> As per compiled bug report, creation of a branch that has a prefix that map to a folder, when that prefix is just an existing branch in the repo fails. > > I.E. 'a/b/c' when 'a/b' just exists.
Yup, that is one of the natural consequences of the design to organize refs in a directory like hierarchies. There are various ref backends (e.g. packed-refs that already exists, and reftable) that could potentially store both D and D/F at the same time, but it is very likely that the higher layer that calls into these ref backends will keep the behaviour as a policy, to ensure that those on older versions of Git can smoothly interoperate with newer versions of Git.
Thanks.