git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.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 12:00:45 -0400	[thread overview]
Message-ID: <20200724160045.GA10590@syl.lan> (raw)
In-Reply-To: <DM5PR1801MB20762477763E6298C7FE6315F0770@DM5PR1801MB2076.namprd18.prod.outlook.com>

Hi Tommaso,

On Fri, Jul 24, 2020 at 10:26:14AM +0000, Tommaso Ercole wrote:
> 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.

This is a known limitation of loose references, since each reference is
stored in a file in $GITDIR/refs.

Reftable support within Git will lift this limitation. In the meantime,
if your references aren't updated you can store them as packed refs
which don't have this limitation, but note that they will be expanded
loose if you touch them again (i.e., this is a good solution for tags,
but not development branches).

Hope that this helps.

> Best regards,
> Tommaso Ercole
> Head Programmer
> Content Delivery

Thanks,
Taylor

  reply	other threads:[~2020-07-24 16:00 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 [this message]
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

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=20200724160045.GA10590@syl.lan \
    --to=me@ttaylorr.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).