From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Jay Soffian <jaysoffian@gmail.com>, Gerd Knops <gerti@bitart.com>,
git@vger.kernel.org
Subject: Re: Possible bug with branch names and case sensitivity
Date: Tue, 22 Nov 2011 10:01:25 -0800 [thread overview]
Message-ID: <7vsjlgdoju.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4ECB315F.4080701@alum.mit.edu> (Michael Haggerty's message of "Tue, 22 Nov 2011 06:21:35 +0100")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> If we want to consider bending git's behavior, there are a number of
> ways we could go:
>
> 1. Remain case-sensitive but prohibit refnames that differ only in case.
I do not see a strong enough reason to be that draconian.
> 2. Remain case-sensitive but prohibit refnames that differ only in case
> *when running on a case-insensitive filesystem*.
If you make it conditional, it should be per-project, not per-repository.
You may be participating in a cross platform project and you may happen to
be on the case-sensitive system, but absense of such a check for you may
end up hurting other participants who work on a case-insensitive one.
> 3. Change the handling of refnames to be case-insensitive but
> case-preserving.
I do not see it is worth the effort. If you were to expend much effort
then I could see in the longer term (now I am talking about Git 2.0 in
this paragraph) one solution is to remove on-filesystem $GIT_DIR/refs/
hierarchy, put it in a trivial database of some sort, keyed with case
sensitive strings.
The transfer of refs over the wire will stay case sensitive so such a
change would be purely local to the repository, so transition would only
matter if you network mount a new style repository and attempt to use with
older version of Git.
If you go that route, we still would need to think about how to deal with
the $GIT_DIR/logs/ hierarchy, though.
prev parent reply other threads:[~2011-11-22 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:08 Possible bug with branch names and case sensitivity Gerd Knops
2011-11-21 19:18 ` Jay Soffian
2011-11-22 5:21 ` Michael Haggerty
2011-11-22 17:31 ` Jay Soffian
2011-11-23 8:54 ` Michael Haggerty
2011-11-23 20:50 ` Ævar Arnfjörð Bjarmason
2011-11-23 22:08 ` Joshua Jensen
2011-11-22 17:49 ` Junio C Hamano
2011-11-23 9:22 ` Michael Haggerty
2011-11-23 18:59 ` Junio C Hamano
2011-11-22 18:01 ` 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
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=7vsjlgdoju.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=gerti@bitart.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=mhagger@alum.mit.edu \
/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).