From: Casey Meijer <cmeijer@strongestfamilies.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: BUG FOLLOWUP: Case insensitivity in worktrees
Date: Thu, 23 Jul 2020 15:20:50 +0000 [thread overview]
Message-ID: <8BABB6F0-517F-4AA0-9FF9-92AF8C33CD0E@strongestfamilies.com> (raw)
In-Reply-To: <EEA65ED1-2BE0-41AD-84CC-780A9F4D9215@strongestfamilies.com>
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.
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 __ ).
Best,
Casey Meijer
next parent reply other threads:[~2020-07-23 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EEA65ED1-2BE0-41AD-84CC-780A9F4D9215@strongestfamilies.com>
2020-07-23 15:20 ` Casey Meijer [this message]
2020-07-24 1:19 ` BUG FOLLOWUP: Case insensitivity in worktrees brian m. carlson
2020-07-24 1:25 ` Junio C Hamano
2020-07-24 18:07 ` Casey Meijer
2020-07-24 18:17 ` Casey Meijer
2020-07-24 19:36 ` Junio C Hamano
2020-07-24 18:14 ` Casey Meijer
2020-07-24 21:09 ` brian m. carlson
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=8BABB6F0-517F-4AA0-9FF9-92AF8C33CD0E@strongestfamilies.com \
--to=cmeijer@strongestfamilies.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.
Code repositories for project(s) associated with this public 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).