Re: BUG FOLLOWUP: Case insensitivity in worktrees

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jul 24, 2020, 01:19 UTC
Message-ID: <20200724011944.GD1758454@crustytoothpaste.net>
In-Reply-To: <8BABB6F0-517F-4AA0-9FF9-92AF8C33CD0E@strongestfamilies.com>

On 2020-07-23 at 15:20:50, Casey Meijer wrote:

Show 6 quoted lines

> This just bit me; it seems quite old, and I wanted to propose an alternative solution (maybe it doesn’t work for some reason I’m unaware of):
> https://marc.info/?l=git&m=154473525401677&w=2
>  
> Why not just preserve the existing semantics of the main worktree by checking the worktree refs first unconditionally and only fall back to the main refs when the ref doesn’t exist locally in the worktree?
>  
> This would have the added benefit of allowing power users to override refs in their worktrees and would, if I’m not mistaken, preserve the semantics of the main worktree in case-insensitive and case-sensitive filesystems.

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?

> Anywho, just a thought.  I could work on a patch if this approach makes sense at least as an intermediary until there’s a pluggable storage backend for non-FS stores 😉   (I'd also be somewhat interested in implementing a postgres/sql storage backend if this project is moving forwards __ ).

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.

-- 
brian m. carlson: Houston, Texas, US