From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: Vadim Kramer <vkokielov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git-Win: case insensitive names
Date: Mon, 1 Jun 2015 20:42:53 +0300 [thread overview]
Message-ID: <20150601204253.50939487ba6e49feb443343e@domain007.com> (raw)
In-Reply-To: <CAFQnHJfK94wG_bpe3OFmd7CyZzLCQFq70QGoMAP8=PchdUVH9g@mail.gmail.com>
On Mon, 1 Jun 2015 13:30:19 -0400
Vadim Kramer <vkokielov@gmail.com> wrote:
> Just had to deal with a nasty cross-UNIX/Windows problem.
>
> Two files in the repository were in the same direcory and had the same
> name differing only by the case of some of the letters. While
> checking them out, git wantonly confused them (conflated them into
> one) and got confused about them.
>
> I know it's an outlandish situation. Still, when git is in a
> case-insensitive file system, it should at least check for this.
What it does it do if you have core.ignorecase set to on?
(And you did tell nothing about your platform and your Git version.)
prev parent reply other threads:[~2015-06-01 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 17:30 Git-Win: case insensitive names Vadim Kramer
2015-06-01 17:42 ` Konstantin Khomoutov [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=20150601204253.50939487ba6e49feb443343e@domain007.com \
--to=kostix+git@007spb.ru \
--cc=git@vger.kernel.org \
--cc=vkokielov@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 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).