From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 2771C1F5AE for ; Fri, 24 Jul 2020 20:36:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726739AbgGXUgM (ORCPT ); Fri, 24 Jul 2020 16:36:12 -0400 Received: from pb-smtp21.pobox.com ([173.228.157.53]:54632 "EHLO pb-smtp21.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726455AbgGXUgM (ORCPT ); Fri, 24 Jul 2020 16:36:12 -0400 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 6CF18DD818; Fri, 24 Jul 2020 16:36:10 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=OBAwWc7ACJJJPMS6taKpmZWUOMo=; b=casQw2 ChwZdezc0gvY0sxp6BouiA44hM/YfbtrB7MVedr2NzEhwhIKZtp8cHl9VVq4wN8v Oj0l9gM7KREh4YXT44Dk/F8WSsVMP5QKoSwA+BMxecY2eFa73xfC53uHeV9AlVSQ Y718jpkYDeLvf5zURgVcH0DxJ8DY4Q1NPHTAs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=YzpUXnl4Y84ETfxl3EP69KKKD+ZlbV1w IBfYkMWL5l0Fk9LVxVOdbreIJoF5FPHJH3qlfhrRyqBSCOJDc8+ChfPs0nMtEFWA 8NT1R6qmxAjF/ShFgHs4BRz009W1ujvyTloGnTkiUYWNRvb19hO+50fTwS0/33Oi KWjOJD/xvMc= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 65905DD817; Fri, 24 Jul 2020 16:36:10 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.196.173.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id A2F5DDD816; Fri, 24 Jul 2020 16:36:07 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Tommaso Ercole Cc: "git\@vger.kernel.org" Subject: Re: Creation of a branch named that has a directory prefix equal to the name of another branch fail. References: Date: Fri, 24 Jul 2020 13:36:05 -0700 In-Reply-To: (Tommaso Ercole's message of "Fri, 24 Jul 2020 10:26:14 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 4D58A3FA-CDED-11EA-B31D-843F439F7C89-77302942!pb-smtp21.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Tommaso Ercole 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.