From: Johannes Sixt <j6t@kdbg.org>
To: martinvz <martin.von.zweigbergk@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Problems with file name case on Windows.
Date: Fri, 23 Apr 2010 08:38:30 +0200 [thread overview]
Message-ID: <4BD14066.3040307@kdbg.org> (raw)
In-Reply-To: <1271969657620-4947131.post@n2.nabble.com>
Am 22.04.2010 22:54, schrieb martinvz:
>
> 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.
The safe way to achieve your goal is:
git mv a b
git mv b A
git commit
-- Hannes
next prev parent reply other threads:[~2010-04-23 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 20:54 Problems with file name case on Windows martinvz
2010-04-23 3:48 ` Tay Ray Chuan
2010-04-23 6:38 ` Johannes Sixt [this message]
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=4BD14066.3040307@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=martin.von.zweigbergk@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).