From: Junio C Hamano <gitster@pobox•com>
To: Karsten Blees <karsten.blees@gmail•com>
Cc: "Johannes Sixt" <j.sixt@viscovery•net>,
"Lee Hopkins" <leerhop@gmail•com>,
"Torsten Bögershausen" <tboegi@web•de>,
git@vger•kernel.org
Subject: Re: Branch Name Case Sensitivity
Date: Fri, 28 Feb 2014 10:58:10 -0800 [thread overview]
Message-ID: <xmqqk3cfuksd.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5310959D.709@gmail.com> (Karsten Blees's message of "Fri, 28 Feb 2014 14:56:45 +0100")
Karsten Blees <karsten.blees@gmail•com> writes:
>> If you are on a case-insensitive filesystem, or work on a cross-platform
>> project, ensure that you avoid ambiguous refs. Problem solved.
>>
>
> So its OK to lose data if you accidentally use an ambiguous ref? I
> cannot believe you actually meant that.
I think he meant what he said: "you avoid ambiguous refs". He did
not say "it is not Git's business to help you doing so".
I think it is prudent to warn in the end-user facing layer (read: do
not touch refs.c to implement something like that) when the user
creates "refs/heads/Next" when there already is "refs/heads/next",
and I further think it would make sense to do so even on case
sensitive platforms.
We warn ambiguous refs across refs hierarchies (e.g. if you have
refs/heads/next and refs/tags/next) with core.warnAmbiguousRefs; I
do not think it is a stretch to either introduce a new configuration
core.warnCaseInsensitiveRefs (auto-detected at the same place as we
auto-detect core.ignorecase) or use the same core.warnAmbiguousRefs
to trigger a warning upon seeing both "refs/heads/next" and
"refs/heads/Next".
next prev parent reply other threads:[~2014-02-28 18:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 21:06 Branch Name Case Sensitivity Lee Hopkins
2014-02-27 19:50 ` Junio C Hamano
2014-02-27 20:32 ` Torsten Bögershausen
2014-02-27 20:37 ` Lee Hopkins
2014-02-27 21:00 ` Michael Haggerty
2014-02-27 22:24 ` Karsten Blees
2014-02-27 23:38 ` Lee Hopkins
2014-02-28 6:41 ` Johannes Sixt
2014-02-28 13:56 ` Karsten Blees
2014-02-28 14:10 ` Lee Hopkins
2014-02-28 18:58 ` Junio C Hamano [this message]
2014-02-28 23:22 ` Duy Nguyen
2014-02-28 23:28 ` Junio C Hamano
2014-03-01 2:42 ` Lee Hopkins
2014-03-01 6:54 ` Torsten Bögershausen
2014-03-01 19:38 ` Lee Hopkins
2014-03-03 10:03 ` Karsten Blees
2014-03-03 14:21 ` Lee Hopkins
2014-03-03 17:51 ` Junio C Hamano
2014-03-04 13:23 ` Karsten Blees
2014-03-04 20:37 ` Torsten Bögershausen
2014-03-05 14:02 ` Lee Hopkins
2014-02-28 9:13 ` Michael Haggerty
2014-02-28 14:31 ` Duy Nguyen
2014-02-28 14:45 ` Michael Haggerty
2014-02-28 9:11 ` Stephen Leake
2014-02-28 9:49 ` Michael Haggerty
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=xmqqk3cfuksd.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=j.sixt@viscovery$(echo .)net \
--cc=karsten.blees@gmail$(echo .)com \
--cc=leerhop@gmail$(echo .)com \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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