From: Junio C Hamano <gitster@pobox.com>
To: Ronnie Sahlberg <sahlberg@google.com>
Cc: Jeff King <peff@peff.net>,
Brian Gernhardt <brian@gernhardtsoftware.com>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH] t1410: Fix for case insensitive filesystems
Date: Sun, 9 Nov 2014 22:34:19 -0800 [thread overview]
Message-ID: <CAPc5daV9g+kio2esi9avj+5ivQyaTkR4mo12gS-Cxt1KCOKMnA@mail.gmail.com> (raw)
In-Reply-To: <20141110062356.GA8047@peff.net>
On Sun, Nov 9, 2014 at 10:23 PM, Jeff King <peff@peff.net> wrote:
> On Sun, Nov 09, 2014 at 08:48:06PM -0500, Brian Gernhardt wrote:
>
>> A pair of recently added tests used branches a and a/b, but earlier
>> tests created files A and A/B. On case insensitive filesystems (such
>> as HFS+), that causes git to complain about the name being ambiguous
>> between branch and file. Resolve by renaming the branches to aa and
>> aa/bb.
>
> Already being discussed here:
>
> http://thread.gmane.org/gmane.comp.version-control.git/259250/focus=259253
>
> :)
Related tangent for a moderately near future.
One thing that we may want to play with around this topic is to try
building an alternative "ref backend" that is backed by a filesystem,
lays out things pretty much the same way as the current "refs" (i.e.
one file per ref, directory hierarchy corresponds to slashes in the
refname, one file per reflog, etc.), but can be stored on a case
insensitive filesystem, as a demonstration of Ronnie's "ref-transaction"
restructuring series.
Perhaps such a backend may store branch 'a' as 'refs/heads/a' while
storing branch 'A' as 'refs/heads/%41' or something, and causes the
right thing to happen when "for-each-ref" enumerates the refs by
unquoting quoted names and when "checkout" asks to check out
such a branch.
prev parent reply other threads:[~2014-11-10 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 1:48 [PATCH] t1410: Fix for case insensitive filesystems Brian Gernhardt
2014-11-10 6:23 ` Jeff King
2014-11-10 6:34 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPc5daV9g+kio2esi9avj+5ivQyaTkR4mo12gS-Cxt1KCOKMnA@mail.gmail.com \
--to=gitster@pobox.com \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sahlberg@google.com \
/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.
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 NNTP newsgroup(s).