git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Han-Wen Nienhuys <hanwen@google.com>
To: Jeff King <peff@peff.net>
Cc: Taylor Blau <me@ttaylorr.com>,
	Tommaso Ercole <Tommaso.Ercole@qlik.com>,
	"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: Mon, 27 Jul 2020 10:51:28 +0200	[thread overview]
Message-ID: <CAFQ2z_O7D_9ToECfMhh3mbRproktM+gTR_-byajatH3+7-ziLg@mail.gmail.com> (raw)
In-Reply-To: <20200724200042.GC4013174@coredump.intra.peff.net>

On Fri, Jul 24, 2020 at 10:00 PM Jeff King <peff@peff.net> wrote:
> [1] I didn't actually check what the current reftable patches do, but
>     that's my recollection from discussions long ago.

struct reftable_write_options has a skip_name_check setting. If set,
it doesn't check for directory/file conflicts. If unset, any attempt
to create such conflicts will API_ERROR from the transaction commit
function.

-- 
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

  parent reply	other threads:[~2020-07-27  8:51 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
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 [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFQ2z_O7D_9ToECfMhh3mbRproktM+gTR_-byajatH3+7-ziLg@mail.gmail.com \
    --to=hanwen@google.com \
    --cc=Tommaso.Ercole@qlik.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.net \
    --subject='Re: Creation of a branch named that has a directory prefix equal to the name of another branch fail.' \
    /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

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).