git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tommaso Ercole <Tommaso.Ercole@qlik.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Creation of a branch named that has a directory prefix equal to the name of another branch fail.
Date: Fri, 24 Jul 2020 13:36:05 -0700	[thread overview]
Message-ID: <xmqqzh7ok5vu.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <DM5PR1801MB20762477763E6298C7FE6315F0770@DM5PR1801MB2076.namprd18.prod.outlook.com> (Tommaso Ercole's message of "Fri, 24 Jul 2020 10:26:14 +0000")

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.

      parent reply	other threads:[~2020-07-24 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM5PR1801MB2076F807C0B9F29A152DBEB7F0760@DM5PR1801MB2076.namprd18.prod.outlook.com>
2020-07-24 10:26 ` Creation of a branch named that has a directory prefix equal to the name of another branch fail Tommaso Ercole
2020-07-24 16:00   ` Taylor Blau
2020-07-24 20:00     ` Jeff King
2020-07-24 20:43       ` Junio C Hamano
2020-07-27  8:21         ` Tommaso Ercole
2020-07-27  9:30           ` Bryan Turner
2020-07-27  8:51       ` Han-Wen Nienhuys
2020-07-24 20:36   ` Junio C Hamano [this message]

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=xmqqzh7ok5vu.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Tommaso.Ercole@qlik.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).