From: Thomas Rast <trast@student.ethz.ch>
To: Yves Goergen <nospam.list@unclassified.de>
Cc: "Holger Hellmuth" <hellmuth@ira.uka.de>,
"Jeff King" <peff@peff.net>, "Carlos Martín Nieto" <cmn@elego.de>,
git@vger.kernel.org, "Erik Faye-Lund" <kusmabite@gmail.com>
Subject: Re: Bug? Git checkout fails with a wrong error message
Date: Thu, 19 Jan 2012 11:24:07 +0100 [thread overview]
Message-ID: <87k44oat2w.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <4F15B65A.8070009@unclassified.de> (Yves Goergen's message of "Tue, 17 Jan 2012 18:56:42 +0100")
Glad that you could fix your repository.
Yves Goergen <nospam.list@unclassified.de> writes:
> Just like that stupid autocrlf that causes more issues than it solves. I
> regularly see files with all lines changed and the diff says that both
> files only differ in line endings. But I have no sure observation on
> whether that value was set or unset in those cases. I'll have to look
> after that, too.
Just please remember what I tried to teach you in this thread: copy and
paste actual command invocations and outputs, and let us do the
interpretation. With CRLF problems, it may in addition help to pipe
through a utility that shows the presence or absence of \r, such as 'cat
-v'.
> These two config settings are not cloned with the repository, are they?
Neither config nor hooks are cloned.
> Also, TortoiseGit already sets ignorecase = true. So maybe the Visual
> Studio provider does the init on its own and is missing that. Or I have
> at some time cloned the repository and the setting wasn't copied over.
git-clone also autodetects the setting as part of initializing the
clone. (Copying over the repository from a case-sensitive medium using
a case-sensitive OS would of course leave it unset.)
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-01-19 10:24 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
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 [this message]
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=87k44oat2w.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=hellmuth@ira.uka.de \
--cc=kusmabite@gmail.com \
--cc=nospam.list@unclassified.de \
--cc=peff@peff.net \
/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.