X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=U7vNC7smSDFmq5a5F3PO4l/XQrtQwo0EIKrwej1KtTT1/H+3ofo0A
	9z3ZqMuRJCKYbbOoHxqma10CBcz0o4O8ZjI9e2pvByDkK1SfU8/q8tnzMUxlJAI5
	kL/v7x7pyrmzppwNHMB/Gzd0LuJiOTPHcxE90L9uF3jkHEHuNlLnQM=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=T1Bzi1i96tkBUjIp32cZodR1Ujg=; b=WpTdYD3O67HPxXh0Bc78BS+YAru+
	wG7+Fy558MD/2E0w5p+v5gZppIIHsq1aQ8O+OkwaOf3MB/uXtl6vh3HjYWK+JWtR
	OBCA7CYSknIRY0y4urd7Yl98vJ+aValT91qBwSk8JsNJV/OYmqQRtW71PVBiN/7v
	tj8Ps24sOK3B+O0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-4.4 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED autolearn=ham version=3.3.2
Date:	Fri, 16 Aug 2013 10:17:43 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Lack of case-sensitive filename handling with git 1.7.9-1 for Cygwin 64-bit
Message-ID:	<20130816081743.GC2562@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAGZiy71u1Ci_2Uw6jgAw3-9gCgwVrS1ae2Bpz9HCbnj2+EZexA AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAGZiy71u1Ci_2Uw6jgAw3-9gCgwVrS1ae2Bpz9HCbnj2+EZexA@mail.gmail.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
X-Virus-Found:	No

--QKdGvSO+nmPlgiQ/
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Aug 16 10:32, Kal Sze wrote:
> I have been using Cygwin 32-bit on Windows 7 Profession 64-bit. I had
> the HKLM\SYSTEM\CurrentControlSet\Control\Session
> Manager\kernel\ObCaseInsensitive registry key set to DWORD 0x00000000
> and case-sensitive filename handling has been fully working in Cygwin
> 32-bit (as far as I can tell from my usage anyway).
>=20
> Now that Cygwin 64-bit has been released, I want to try it. I notice
> that git in Cygwin 64-bit does not seem to correctly handle filesname
> that differ only by case.
>=20
> To reproduce, create a repository in Cygwin 32-bit *with the
> aforementioned registry key set*:
>=20
>     $ git init case_sensitivity_test; cd case_sensitivity_test
>=20
> Create two files of different content with similar filenames that
> differ only by case:
>=20
>     $ echo 'FOO' > FOO.TXT; echo 'foo' > foo.txt
>=20
> Commit them into the repository:
>=20
>     $ git add .; git commit -m 'Initial commit'
>     [master (root-commit) 16d1b59] Initial commit
>      2 files changed, 2 insertions(+), 0 deletions(-)
>      create mode 100644 FOO.TXT
>      create mode 100644 foo.txt
>=20
> In Cygwin 32-bit, this looks all green:
>=20
>     $ git status
>     # On branch master
>     nothing to commit (working directory clean)
>     $ ls
>     FOO.TXT  foo.txt
>=20
> Now, fire up the Cygwin64 terminal and browse to the repository, then:
>=20
>     $ ls
>     FOO.TXT  foo.txt
>     $ cat FOO.TXT
>     FOO
>     $ cat foo.txt
>     foo
>=20
> So `ls` and `cat` both recognize the two different files. However:
>=20
>     $ git status
>     # On branch master
>     # Changes not staged for commit:
>     #   (use "git add <file>..." to update what will be committed)
>     #   (use "git checkout -- <file>..." to discard changes in working
> directory)
>     #
>     #       modified:   foo.txt
>     #
>     no changes added to commit (use "git add" and/or "git commit -a")
>=20
> "Oops."

The interesting thing here is, if you try this the other way
around, you'll see the exact same effect.  If you created the
above git repo with 64 bit git, everything works exactly as in
the 32 bit version and the two files are correctly recognized.

I assume the format of the git database files depends on the
architecture.  Therefore it's probably not advisable to use
a git repo created under 32 bit git with a 64 bit git and vice
versa.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--QKdGvSO+nmPlgiQ/
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJSDeAnAAoJEPU2Bp2uRE+gK6wP/1Vp2jdOsjv0GBkYfSyBd7QH
9k/8sGG24Ud+xBpRLRdC4+urw2r1Ui/DaujkdlpZppZFePidtcaUdU/vbnPdHrVn
ZYRhPkPbPQLl7khREacpLAiyF9pDB5t+WPgXmp/n05sQ1kXEcaP4Er4tOz5zCS05
0ZdX56eDY0AG293l/1JPicD09/1FmeXs9xXaTMoM/s/0WgEFB8cbQ+A/DhooqJ1R
JFytHi6FyytiQH9xhGpiJEQ+G+B44hh1iAacpLgSCkODpp41qVvQy0BSDmtYpWMT
fL2L/i1eMC5VwKyp/hySn71KJ7fVBM1dNhb/g1k/mXpd2DYn2OEnlHVHNYIxHGFD
nMmcruHZVJrMkKUxlGC9H05QELmA+SeN/pCEt6E0RD18Plf5Dy4W6lwgH+gBwE90
5X2jteUfa2LBtQwT4mNe1lWvB5yOJcDJRcAYVG3yS/SQVFqifiYoHKHLnSEpMoDr
9A0a3U7R9/6wcGmkf1J2fs1sN7ZfDKUxHQzB3Xeu87EMkR2EvCI82Jq8t57Y9aDe
EDU7IBCj/6t3EO4mnY3P4KIJa5p1z2YH6xr8OjaaX8RzEYIAjGRvSlVlFR+Smq5x
7KdZok1Vxir8kak/jEtHIPAkNiJtieI/3/WIBXArPgq4zeufx9gUezOZPhTb4aPG
zGDV3+PDMn3t5y6Kn/6I
=7kRu
-----END PGP SIGNATURE-----

--QKdGvSO+nmPlgiQ/--

- Raw text -