From: martinvz <martin.von.zweigbergk@gmail.com>
To: git@vger.kernel.org
Subject: Problems with file name case on Windows.
Date: Thu, 22 Apr 2010 12:54:17 -0800 (PST) [thread overview]
Message-ID: <1271969657620-4947131.post@n2.nabble.com> (raw)
Under Cygwin, if you add a file "a" in one commit, then rename the file to
"A" and commit again, both files will be in the new commit. Running the
following line under Cygwin produces a commit with both files ("a" and "A").
Running it on Linux produces a commit with one file ("A"), as expected.
git init; git config core.ignorecase false; touch a; git add a; git commit
-m a; mv a A; git add -A; git commit -m A
The problem seems to be with the "git add -A" part, since it is possible to
get around the problem by running "git add A" followed by "git rm a" (or by
using lower-level commands, I suppose). What are the chances of getting this
fixed? It's mostly annoying when importing existing code where it's harder
to use the add-rm workaround, since you don't know which files have changed
file name case.
--
View this message in context: http://git.661346.n2.nabble.com/Problems-with-file-name-case-on-Windows-tp4947131p4947131.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2010-04-22 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 20:54 martinvz [this message]
2010-04-23 3:48 ` Problems with file name case on Windows Tay Ray Chuan
2010-04-23 6:38 ` Johannes Sixt
2010-04-23 12:16 ` martinvz
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=1271969657620-4947131.post@n2.nabble.com \
--to=martin.von.zweigbergk@gmail.com \
--cc=git@vger.kernel.org \
/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).