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 BA3C21F5AE for ; Fri, 24 Jul 2020 01:26:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727096AbgGXBZy (ORCPT ); Thu, 23 Jul 2020 21:25:54 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]:56234 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726947AbgGXBZy (ORCPT ); Thu, 23 Jul 2020 21:25:54 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id DD2BE6E464; Thu, 23 Jul 2020 21:25:51 -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=xIETkcrcuTkDDHBOIwvPpyIpZwM=; b=puo/W1 qXPZymT4YrGaZwnxedrsfqbVt2HWNNeHtx9quYtiLNCbCgu4TpenvSnN7EGCeyyC Xpu05FoDqJ4aHfBYMJthVKhJVVlduz1MPQPSttb5WA6Wa8Bz6pUzKnOxK1WRcqyf L/TfqjboppM9IWD/FibGfSzXhH4+mHyiK8lWk= 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=qk17rcqKf5N/HrcXWfcMBvUaqF1dwUTO 78bHFoLs6aFzMEFhNMX3/5A24aQyUnCu41JRq6/MdJyPQV1uFEUf9EQPfYJsc2fT IaBEYMJOWNnx+iz0xyFK/9TqSwjI1DMPCfLS9y+sNnsP9esn9tYXXh1KYTmSR2hC WTBrRI7OA5M= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id D4D606E463; Thu, 23 Jul 2020 21:25:51 -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-smtp1.pobox.com (Postfix) with ESMTPSA id 641A56E462; Thu, 23 Jul 2020 21:25:51 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: "brian m. carlson" Cc: Casey Meijer , "git\@vger.kernel.org" Subject: Re: BUG FOLLOWUP: Case insensitivity in worktrees References: <8BABB6F0-517F-4AA0-9FF9-92AF8C33CD0E@strongestfamilies.com> <20200724011944.GD1758454@crustytoothpaste.net> Date: Thu, 23 Jul 2020 18:25:50 -0700 In-Reply-To: <20200724011944.GD1758454@crustytoothpaste.net> (brian m. carlson's message of "Fri, 24 Jul 2020 01:19:44 +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: 9C73CD80-CD4C-11EA-BE6E-01D9BED8090B-77302942!pb-smtp1.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org "brian m. carlson" writes: > It isn't clear to me exactly what you're suggesting. Are you suggesting > that we allow "head" instead of "HEAD" in worktrees, or that we allow > refs in general to be case insensitive, or something else? > There is a proposal for a ref storage backend called "reftable" which > will not store the ref names in the file system, and work is being done > on it. There has been a suggestion for an SQLite store in the past, but > that causes problems for certain implementations, such as JGit, which do > not want to have C bindings. Yes, another important thing to point out is that one shared goal of these efforts is so that users, even those on case insensitive filesystems, can name their refs foo and FOO and have the system treat these as two distinct refs. IOW, wanting to enhance "support" for case insensitive treatment of refs will not fly---asking for "head" and getting contents of "HEAD" on certain platforms is a bug, induced by limited filesystem these platforms use, and it is being fixed. Thanks.