From: Tommaso Ercole <Tommaso.Ercole@qlik.com>
To: "firstname.lastname@example.org" <email@example.com>
Subject: Creation of a branch named that has a directory prefix equal to the name of another branch fail.
Date: Fri, 24 Jul 2020 10:26:14 +0000 [thread overview]
Message-ID: <DM5PR1801MB20762477763E6298C7FE6315F0770@DM5PR1801MB2076.namprd18.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
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.
Mobile: +39 328 7182833
via Brescia 31
36040 Torri di Quartesolo - Vicenza - Italy
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
[-- Attachment #2: git-bugreport-2020-07-23-1754.txt --]
[-- Type: text/plain, Size: 739 bytes --]
Creating a branch a/b/c when a/b exists fails complaining that a ref 'a/b' just exists.
This is probably due to the fact that when creating a/b a directory 'a' is created inside
'refs/heads' and a file 'b' is created under the a directory, avoiding the subsequent possibility
to create a folder 'b' in the same directory that is needed to create the ref for 'a/b/c'
The solution seems to append to the file an extension to disambiguate the file from the folder.
git version 2.27.0.windows.1
built from commit: 907ab1011dce9112700498e034b974ba60f8b407
uname: Windows 10.0 18363
compiler info: gnuc: 10.1
libc info: no libc information available
next parent reply other threads:[~2020-07-24 10:26 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 ` Tommaso Ercole [this message]
2020-07-24 16:00 ` Creation of a branch named that has a directory prefix equal to the name of another branch fail 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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).