Re: Why don't git-init and git-clone probe for core.ignorecase on Windows > XP?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Junio, this question was due to a misunderstanding on my part:

For some reason, I thought "probe" in the man meant asking the user
whether core.ignorecase should be set. I vaguely recall there's
another (also Windows-related) setting that is interactively queried
like that.

Following your reply I tested with recent (1.7) installations of
msysgit and core.ignorecase is set automatically to true in
.git/config for newly created / cloned repo on NTFS over Windows 7.

Thanks again and sorry for the misunderstanding, D.

On Fri, Jan 7, 2011 at 2:18 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Dun Peal <dunpealer@xxxxxxxxx> writes:
>
>> The git-config manpage says about core.ignorecase:
>>
>> "The default is false, except git-clone(1) or git-init(1) will probe
>> and set core.ignorecase true if appropriate when the repository is
>> created."
>>
>> I assume this is happening when you clone or init on FAT, which is
>> explicitly mentioned earlier in that section. But apparently it
>> doesn't happen for either XP, Vista or 7. While those newer releases
>> use NTFS, which technically supports case-sensitivity, the operating
>> itself still apparently doesn't, so it would seem like git-clone and
>> git-init should probe regarding the core.ignorecase on any version of
>> Windows, no?
>
> Sorry, but it is unclear if you are complaining that core.ignorecase is
> set (but you believe it shouldn't be) or it is not set (but you believe it
> should be) on NTFS from the description.
>
> As far as I can tell from the code (I obviously only look at the plain
> vanilla git, and msysgit might have some patch to this part, I dunno.  Oh
> by the way you didn't say which version you are complaining about,
> either), we do the probing on all systems (including POSIX folks with FAT
> filesystem mounted) by first creating .git/config and then checking if a
> file .git/CoNfIg which we know we never created can be accessed.  If we
> can, that means the filesystem ignores case, iow, we cannot have two files
> config and CoNfIg at the same time, and set core.ignorecase to true.
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]