git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Yves Goergen <nospam.list@unclassified.de>
Cc: "Holger Hellmuth" <hellmuth@ira.uka.de>,
	git@vger.kernel.org, "Carlos Martín Nieto" <cmn@elego.de>
Subject: Re: Bug? Git checkout fails with a wrong error message
Date: Mon, 16 Jan 2012 16:27:09 -0500	[thread overview]
Message-ID: <20120116212709.GA21770@sigill.intra.peff.net> (raw)
In-Reply-To: <4F1494AA.1000004@unclassified.de>

On Mon, Jan 16, 2012 at 10:20:42PM +0100, Yves Goergen wrote:

> On 16.01.2012 20:09 CE(S)T, Jeff King wrote:
> > What is the output of "git config core.ignorecase" in your repository?
> 
> None, i.e. an empty line.

That's odd. When the repository is first created, git will do a test to
see whether the filesystem supports case-sensitivity, and will set
core.ignorecase if it does not. Might this repository have been created
on a different filesystem, and then moved onto the case-insensitive
filesystem?

Or might it have been created by something other than core git? I don't
know whether one can create a repo in TortoiseGit, or if so how it does
so.

In any case, try doing:

  git config core.ignorecase true

and see if that clears up your problems.

-Peff

  reply	other threads:[~2012-01-16 21:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 18:44 Bug? Git checkout fails with a wrong error message Yves Goergen
2012-01-13 12:50 ` Holger Hellmuth
2012-01-13 17:46   ` Yves Goergen
2012-01-13 19:28     ` Holger Hellmuth
2012-01-15  8:14       ` Yves Goergen
2012-01-16 11:07         ` Holger Hellmuth
2012-01-16 18:50           ` Yves Goergen
2012-01-16 19:09             ` Jeff King
2012-01-16 21:20               ` Yves Goergen
2012-01-16 21:27                 ` Jeff King [this message]
2012-01-17  7:41                   ` Yves Goergen
2012-01-16 19:17             ` Thomas Rast
     [not found]               ` <4F152767.9010104@unclassified.de>
2012-01-17  8:45                 ` Thomas Rast
2012-01-17 17:56                   ` Yves Goergen
2012-01-19 10:24                     ` Thomas Rast
2012-01-16 21:18             ` Erik Faye-Lund
2012-01-16 18:58           ` Yves Goergen
2012-01-13 17:37 ` Bug! Git merge also " Yves Goergen
2012-01-13 17:50   ` Jeff King
2012-01-13 18:49     ` Yves Goergen
2012-01-13 18:54       ` Jeff King
2012-01-13 19:05         ` Yves Goergen
2012-01-13 17:56   ` Carlos Martín Nieto
2012-01-13 18:59     ` Yves Goergen
2012-01-13 19:34       ` Jakub Narebski
2012-01-15  8:17         ` Yves Goergen
2012-01-15 10:08           ` Jakub Narebski

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=20120116212709.GA21770@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=hellmuth@ira.uka.de \
    --cc=nospam.list@unclassified.de \
    /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).