From: Junio C Hamano <gitster@pobox.com>
To: Lee Hopkins <leerhop@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Branch Name Case Sensitivity
Date: Thu, 27 Feb 2014 11:50:45 -0800 [thread overview]
Message-ID: <xmqqvbw0xrl6.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJHY66EQD280QgXBCoZU4y_aqSEu3A1hXzeW7X-rtT6vMZ92oA@mail.gmail.com> (Lee Hopkins's message of "Wed, 26 Feb 2014 16:06:54 -0500")
Lee Hopkins <leerhop@gmail.com> writes:
> Last week I ran across a potential bug with branch names on case
> insensitive file systems, the complete scenario can be found here:
>
> https://groups.google.com/forum/#!topic/msysgit/ugKL-sVMiqI
>
> The tldr is because refs are stored as plain text files except when
> packed into packed-refs, Git occasionally cannot tell the difference
> between branches whose names only differ in case, and this could
> potentially lead to the loss of history.
>
> It sounds like this is a known issue, and after some more digging I
> did find some older threads related to this topic, but nothing recent.
Yes, it is not limited to branch names but also applies to tags and
filenames in your working tree.
Perhaps git-{branch,tag}.txt and possibly gitrepository-layout.txt
in Documentation/ may need a new "*Note*" section to warn against
this.
Thanks.
next prev parent reply other threads:[~2014-02-27 19:50 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 [this message]
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
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=xmqqvbw0xrl6.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=leerhop@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.