{"thread":{"id":"48771","subject":"[PATCH] Documentation: declare \"core.ignorecase\" as internal variable","startedAt":"2018-06-24T10:05:24Z","lastAt":"2018-06-28T17:03:53Z","messageCount":12,"participants":["Marc Strapetz","Eric Sunshine","Sascha Silbe","Torsten Bögershausen","Junio C Hamano","Aaron Schrab"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"350794","messageId":"7f6b2a42-334d-9443-7b89-625069931ca7@syntevo.com","threadId":"48771","inReplyTo":null,"subject":"[PATCH] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Marc Strapetz","fromEmail":"marc.strapetz@syntevo.com","sentAt":"2018-06-24T10:05:21Z","receivedAt":"2018-06-24T10:05:24Z","isPatch":true,"sender":{"key":"marc.strapetz@syntevo.com","avatar":"https://avatars.githubusercontent.com/u/3380730?v=4"},"body":"The current description of \"core.ignorecase\" reads like an option which\nis intended to be changed by the user while it's actually expected to\nbe set by Git only [1].\n\n[1] https://marc.info/?l=git&m=152972992729761&w=2\n\nSigned-off-by: Marc Strapetz \n---\n Documentation/config.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex ab641bf5a..c25693828 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -390,7 +390,7 @@ core.hideDotFiles::\n \tdefault mode is 'dotGitOnly'.\n\n core.ignoreCase::\n-\tIf true, this option enables various workarounds to enable\n+\tInternal variable which enables various workarounds to enable\n \tGit to work better on filesystems that are not case sensitive,\n \tlike FAT. For example, if a directory listing finds\n \t\"makefile\" when Git expects \"Makefile\", Git will assume\n@@ -399,7 +399,7 @@ core.ignoreCase::\n +\n The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n will probe and set core.ignoreCase true if appropriate when the repository\n-is created.\n+is created. Modifying this value afterwards may result in unexpected \nbehavior.\n\n core.precomposeUnicode::\n \tThis option is only used by Mac OS implementation of Git.\n-- \n2.17.0.rc0.3.gb1b5a51b2\n\n"},{"id":"350796","messageId":"CAPig+cRu8UGVB3MYNRN_Jn0w8Vn=+WdG488hmaePzP=ibtU3TQ@mail.gmail.com","threadId":"48771","inReplyTo":"7f6b2a42-334d-9443-7b89-625069931ca7@syntevo.com","subject":"Re: [PATCH] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2018-06-24T10:19:16Z","receivedAt":"2018-06-24T10:19:30Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Sun, Jun 24, 2018 at 6:05 AM Marc Strapetz wrote:\n> The current description of \"core.ignorecase\" reads like an option which\n> is intended to be changed by the user while it's actually expected to\n> be set by Git only [1].\n>\n> [1] https://marc.info/?l=git&m=152972992729761&w=2\n\nThanks for following up the discussion with a patch.\n\nThe commit message, unfortunately, doesn't explain the \"why\" of this\nchange in enough detail for someone to understand the issue without\nchasing down that link (which could go stale, or the reader might be\noffline). Incorporating Bryan's explanation[1] directly into the\ncommit message would likely be a good idea if you happen to re-roll.\n\n Git on Windows is not designed to run with anything other than\n core.ignoreCase=true, and attempting to do so will cause\n unexpected behavior. In other words, it's not a behavior toggle so\n user's can request the functionality to work one way or the other;\n it's an implementation detail that `git init` and `git clone` set\n when a repository is created purely so they don't have to probe\n the file system each time you run a `git` command.\n\n[1]: https://public-inbox.org/git/CAGyf7-GvcN8EhMgtaZcDJNYNdfLwVH8HVBDmZqJU40nze0NSEA@mail.gmail.com/\n\n> Signed-off-by: Marc Strapetz \n"},{"id":"350798","messageId":"aa841316-5fc0-b69b-a3d0-15911b0776f4@syntevo.com","threadId":"48771","inReplyTo":"7f6b2a42-334d-9443-7b89-625069931ca7@syntevo.com","subject":"[PATCH v2] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Marc Strapetz","fromEmail":"marc.strapetz@syntevo.com","sentAt":"2018-06-24T10:44:26Z","receivedAt":"2018-06-24T10:44:30Z","isPatch":true,"sender":{"key":"marc.strapetz@syntevo.com","avatar":"https://avatars.githubusercontent.com/u/3380730?v=4"},"body":"The current description of \"core.ignoreCase\" reads like an option which\nis intended to be changed by the user while it's actually expected to\nbe set by Git on initialization only. This is especially important for\nGit for Windows, as noted by Bryan Turner [1]:\n\n Git on Windows is not designed to run with anything other than\n core.ignoreCase=true, and attempting to do so will cause\n unexpected behavior. In other words, it's not a behavior toggle so\n user's can request the functionality to work one way or the other;\n it's an implementation detail that `git init` and `git clone` set\n when a repository is created purely so they don't have to probe\n the file system each time you run a `git` command.\n\n[1] https://marc.info/?l=git&m=152972992729761&w=2\n\nSigned-off-by: Marc Strapetz \n---\n Documentation/config.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex ab641bf5a..c25693828 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -390,7 +390,7 @@ core.hideDotFiles::\n \tdefault mode is 'dotGitOnly'.\n\n core.ignoreCase::\n-\tIf true, this option enables various workarounds to enable\n+\tInternal variable which enables various workarounds to enable\n \tGit to work better on filesystems that are not case sensitive,\n \tlike FAT. For example, if a directory listing finds\n \t\"makefile\" when Git expects \"Makefile\", Git will assume\n@@ -399,7 +399,7 @@ core.ignoreCase::\n +\n The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n will probe and set core.ignoreCase true if appropriate when the repository\n-is created.\n+is created. Modifying this value afterwards may result in unexpected \nbehavior.\n\n core.precomposeUnicode::\n \tThis option is only used by Mac OS implementation of Git.\n-- \n2.17.0.rc0.3.gb1b5a51b2\n"},{"id":"350799","messageId":"toe7emobf3h.fsf@mimosa.sascha.silbe.org","threadId":"48771","inReplyTo":"aa841316-5fc0-b69b-a3d0-15911b0776f4@syntevo.com","subject":"Re: [PATCH v2] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Sascha Silbe","fromEmail":"sascha-ml-reply-to-2018-3@silbe.org","sentAt":"2018-06-24T11:26:10Z","receivedAt":"2018-06-24T11:40:04Z","isPatch":true,"sender":{"key":"sascha-ml-reply-to-2018-3@silbe.org","avatar":null},"body":"Hello Bryan, hello Marc,\n\nMarc Strapetz writes:\n\n> The current description of \"core.ignoreCase\" reads like an option which\n> is intended to be changed by the user while it's actually expected to\n> be set by Git on initialization only. This is especially important for\n> Git for Windows, as noted by Bryan Turner [1]:\n\nDoes this apply to Mac OS X as well? I helped someone recently who had\ntrouble with renamed files (case change only) in a repository residing\non a case-insensitive HFS+ file system. Setting core.ignoreCase\nexplicitly (apparently it didn't get set automatically during clone for\nsome reason) helped; the files are recognised correctly now and the\ncase-only rename could be pulled. Is the post-clone change insufficient\non Mac OS X? Do we need to replace the existing repository and clone\nagain using '--config core.ignoreCase=true' to avoid future issues?\n\n\nPS: Including the message-id of the mail being referenced would be\n useful; the id in the URL you gave is specific to the service being\n used (public-inbox.org) and cannot be used to reference the mail in\n any other archive (local or public). If you use the mid:\n syntax (RFC 1630) some MUAs can even recognise the link and open the\n mail directly.\n\nSascha\n-- \nSoftwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg\nhttps://se-silbe.de/\nUSt-IdNr.: DE281696641\n"},{"id":"350801","messageId":"20180624134743.GA31295@tor.lan","threadId":"48771","inReplyTo":"aa841316-5fc0-b69b-a3d0-15911b0776f4@syntevo.com","subject":"Re: [PATCH v2] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2018-06-24T13:47:43Z","receivedAt":"2018-06-24T13:47:52Z","isPatch":true,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Sun, Jun 24, 2018 at 12:44:26PM +0200, Marc Strapetz wrote:\n> The current description of \"core.ignoreCase\" reads like an option which\n> is intended to be changed by the user while it's actually expected to\n> be set by Git on initialization only. This is especially important for\n> Git for Windows, as noted by Bryan Turner [1]:\n> \n> Git on Windows is not designed to run with anything other than\n> core.ignoreCase=true, and attempting to do so will cause\n> unexpected behavior. In other words, it's not a behavior toggle so\n> user's can request the functionality to work one way or the other;\n> it's an implementation detail that `git init` and `git clone` set\n> when a repository is created purely so they don't have to probe\n> the file system each time you run a `git` command.\n\nThis is a nice explanation, thanaks for that,\nSome users of Mac OS or SAMBA will see core.ignoreCase=true, and are not\nsupposed to change it.\n\nThe same explanation (Git for Windows)\nis alse valid for HFS+ and APFS under Mac OS and VFAT under all OS.\n(or even an ext4 file system under Linux exported to Mac OS using SAMBA)\n\nMay be something like this?\n\n Git on a case insensitve file system (Windows, Mac OS, VFAT, SAMBA)\n is not designed to run with anything other than\n core.ignoreCase=true, and attempting to do so will cause\n unexpected behavior. In other words, it's not a behavior toggle so\n .....\n\n\n\n> \n> [1] https://marc.info/?l=git&m=152972992729761&w=2\n> \n> Signed-off-by: Marc Strapetz \n> ---\n> Documentation/config.txt | 4 ++--\n> 1 file changed, 2 insertions(+), 2 deletions(-)\n> \n> diff --git a/Documentation/config.txt b/Documentation/config.txt\n> index ab641bf5a..c25693828 100644\n> --- a/Documentation/config.txt\n> +++ b/Documentation/config.txt\n> @@ -390,7 +390,7 @@ core.hideDotFiles::\n> \tdefault mode is 'dotGitOnly'.\n> \n> core.ignoreCase::\n> -\tIf true, this option enables various workarounds to enable\n> +\tInternal variable which enables various workarounds to enable\n> \tGit to work better on filesystems that are not case sensitive,\n> \tlike FAT. For example, if a directory listing finds\n> \t\"makefile\" when Git expects \"Makefile\", Git will assume\n> @@ -399,7 +399,7 @@ core.ignoreCase::\n> +\n> The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n> will probe and set core.ignoreCase true if appropriate when the repository\n> -is created.\n> +is created. Modifying this value afterwards may result in unexpected\n> behavior.\n> \n> core.precomposeUnicode::\n> \tThis option is only used by Mac OS implementation of Git.\n> -- \n> 2.17.0.rc0.3.gb1b5a51b2\n"},{"id":"351042","messageId":"c899089d-c195-26b5-66ce-de0273a7152b@syntevo.com","threadId":"48771","inReplyTo":"7f6b2a42-334d-9443-7b89-625069931ca7@syntevo.com","subject":"[PATCH v3] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Marc Strapetz","fromEmail":"marc.strapetz@syntevo.com","sentAt":"2018-06-26T21:50:56Z","receivedAt":"2018-06-26T21:51:00Z","isPatch":true,"sender":{"key":"marc.strapetz@syntevo.com","avatar":"https://avatars.githubusercontent.com/u/3380730?v=4"},"body":"The current description of \"core.ignoreCase\" reads like an option which\nis intended to be changed by the user while it's actually expected to\nbe set by Git on initialization only. Subsequently, Git relies on the\nproper configuration of this variable, as noted by Bryan Turner [1]:\n\n Git on a case-insensitive filesystem (APFS, HFS+, FAT32, exFAT,\n vFAT, NTFS, etc.) is not designed to be run with anything other\n than core.ignoreCase=true.\n\n[1] https://marc.info/?l=git&m=152998665813997&w=2\n mid:CAGyf7-GeE8jRGPkME9rHKPtHEQ6P1+ebpMMWAtMh01uO3bfy8w@mail.gmail.com\n\nSigned-off-by: Marc Strapetz \n---\n Documentation/config.txt | 9 ++++++---\n 1 file changed, 6 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 1cc18a828..c70cfe956 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -390,16 +390,19 @@ core.hideDotFiles::\n \tdefault mode is 'dotGitOnly'.\n\n core.ignoreCase::\n-\tIf true, this option enables various workarounds to enable\n+\tInternal variable which enables various workarounds to enable\n \tGit to work better on filesystems that are not case sensitive,\n-\tlike FAT. For example, if a directory listing finds\n-\t\"makefile\" when Git expects \"Makefile\", Git will assume\n+\tlike APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing\n+\tfinds \"makefile\" when Git expects \"Makefile\", Git will assume\n \tit is really the same file, and continue to remember it as\n \t\"Makefile\".\n +\n The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n will probe and set core.ignoreCase true if appropriate when the repository\n is created.\n++\n+Git relies on the proper configuration of this variable for your operating\n+and file system. Modifying this value may result in unexpected behavior.\n\n core.precomposeUnicode::\n \tThis option is only used by Mac OS implementation of Git.\n-- \n2.17.0.rc0.3.gb1b5a51b2\n\n"},{"id":"351153","messageId":"xmqqzhzgdoyb.fsf@gitster-ct.c.googlers.com","threadId":"48771","inReplyTo":"c899089d-c195-26b5-66ce-de0273a7152b@syntevo.com","subject":"Re: [PATCH v3] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-06-27T19:11:40Z","receivedAt":"2018-06-27T19:11:48Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Marc Strapetz writes:\n\n> [1. text/plain]\n> The current description of \"core.ignoreCase\" reads like an option which\n> is intended to be changed by the user while it's actually expected to\n> be set by Git on initialization only. Subsequently, Git relies on the\n> proper configuration of this variable, as noted by Bryan Turner [1]:\n> \n> Git on a case-insensitive filesystem (APFS, HFS+, FAT32, exFAT,\n> vFAT, NTFS, etc.) is not designed to be run with anything other\n> than core.ignoreCase=true.\n> \n> [1] https://marc.info/?l=git&m=152998665813997&w=2\n> mid:CAGyf7-GeE8jRGPkME9rHKPtHEQ6P1+ebpMMWAtMh01uO3bfy8w@mail.gmail.com\n> \n> Signed-off-by: Marc Strapetz \n> ---\n> Documentation/config.txt | 9 ++++++---\n> 1 file changed, 6 insertions(+), 3 deletions(-)\n> \n\nHmph. Do other people have difficulty applying this patch to their\ntrees? It is just several lines long so I could retype it myself,\nbut I guess \"Content-Type: text/plain; charset=utf-8; format=flowed\"\nhas destroyed formatting of the patch rather badly.\n\n> diff --git a/Documentation/config.txt b/Documentation/config.txt\n> index 1cc18a828..c70cfe956 100644\n> --- a/Documentation/config.txt\n> +++ b/Documentation/config.txt\n> @@ -390,16 +390,19 @@ core.hideDotFiles::\n> \tdefault mode is 'dotGitOnly'.\n>\n> core.ignoreCase::\n> -\tIf true, this option enables various workarounds to enable\n> +\tInternal variable which enables various workarounds to enable\n> \tGit to work better on filesystems that are not case sensitive,\n> -\tlike FAT. For example, if a directory listing finds\n> -\t\"makefile\" when Git expects \"Makefile\", Git will assume\n> +\tlike APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing\n> +\tfinds \"makefile\" when Git expects \"Makefile\", Git will assume\n> \tit is really the same file, and continue to remember it as\n> \t\"Makefile\".\n> +\n> The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n> will probe and set core.ignoreCase true if appropriate when the repository\n> is created.\n> ++\n> +Git relies on the proper configuration of this variable for your operating\n> +and file system. Modifying this value may result in unexpected behavior.\n>\n> core.precomposeUnicode::\n> \tThis option is only used by Mac OS implementation of Git.\n"},{"id":"351180","messageId":"20180627230957.GB15174@pug.qqx.org","threadId":"48771","inReplyTo":"xmqqzhzgdoyb.fsf@gitster-ct.c.googlers.com","subject":"Re: [PATCH v3] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Aaron Schrab","fromEmail":"aaron@schrab.com","sentAt":"2018-06-27T23:09:57Z","receivedAt":"2018-06-27T23:16:16Z","isPatch":true,"sender":{"key":"aaron@schrab.com","avatar":"https://avatars.githubusercontent.com/u/39620?v=4"},"body":"At 12:11 -0700 27 Jun 2018, Junio C Hamano wrote:\n>Hmph. Do other people have difficulty applying this patch to their\n>trees? It is just several lines long so I could retype it myself,\n>but I guess \"Content-Type: text/plain; charset=utf-8; format=flowed\"\n>has destroyed formatting of the patch rather badly.\n\nYes, format=flowed requires lines that start with a space (along with \n'>' or 'From ') to be space-stuffed, adding a leading space. This will \naffect context lines in patches.\n\nI was able to apply it cleanly (I think) by sending the message to: \n\n sed '/@@/,$s/^ / /' | git am\n\nThat's replacing two leading spaces with one.\n"},{"id":"351198","messageId":"20180628112157.17176-1-marc.strapetz@syntevo.com","threadId":"48771","inReplyTo":"7f6b2a42-334d-9443-7b89-625069931ca7@syntevo.com","subject":"[PATCH v4] Documentation: declare \"core.ignoreCase\" as internal variable","fromName":"Marc Strapetz","fromEmail":"marc.strapetz@syntevo.com","sentAt":"2018-06-28T11:21:57Z","receivedAt":"2018-06-28T11:22:35Z","isPatch":true,"sender":{"key":"marc.strapetz@syntevo.com","avatar":"https://avatars.githubusercontent.com/u/3380730?v=4"},"body":"The current description of \"core.ignoreCase\" reads like an option which\nis intended to be changed by the user while it's actually expected to\nbe set by Git on initialization only. Subsequently, Git relies on the\nproper configuration of this variable, as noted by Bryan Turner [1]:\n\n Git on a case-insensitive filesystem (APFS, HFS+, FAT32, exFAT,\n vFAT, NTFS, etc.) is not designed to be run with anything other\n than core.ignoreCase=true.\n\n[1] https://marc.info/?l=git&m=152998665813997&w=2\n mid:CAGyf7-GeE8jRGPkME9rHKPtHEQ6P1+ebpMMWAtMh01uO3bfy8w@mail.gmail.com\n\nSigned-off-by: Marc Strapetz \n---\n Documentation/config.txt | 9 ++++++---\n 1 file changed, 6 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 1cc18a828..c70cfe956 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -390,16 +390,19 @@ core.hideDotFiles::\n \tdefault mode is 'dotGitOnly'.\n \n core.ignoreCase::\n-\tIf true, this option enables various workarounds to enable\n+\tInternal variable which enables various workarounds to enable\n \tGit to work better on filesystems that are not case sensitive,\n-\tlike FAT. For example, if a directory listing finds\n-\t\"makefile\" when Git expects \"Makefile\", Git will assume\n+\tlike APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing\n+\tfinds \"makefile\" when Git expects \"Makefile\", Git will assume\n \tit is really the same file, and continue to remember it as\n \t\"Makefile\".\n +\n The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n will probe and set core.ignoreCase true if appropriate when the repository\n is created.\n++\n+Git relies on the proper configuration of this variable for your operating\n+and file system. Modifying this value may result in unexpected behavior.\n \n core.precomposeUnicode::\n \tThis option is only used by Mac OS implementation of Git.\n-- \n2.17.0.rc0.3.gb1b5a51b2\n\n"},{"id":"351199","messageId":"8f01e60e-2f4f-49dd-277a-845363554fa9@syntevo.com","threadId":"48771","inReplyTo":"xmqqzhzgdoyb.fsf@gitster-ct.c.googlers.com","subject":"Re: [PATCH v3] Documentation: declare \"core.ignorecase\" as internal variable","fromName":"Marc Strapetz","fromEmail":"marc.strapetz@syntevo.com","sentAt":"2018-06-28T11:36:22Z","receivedAt":"2018-06-28T11:42:20Z","isPatch":true,"sender":{"key":"marc.strapetz@syntevo.com","avatar":"https://avatars.githubusercontent.com/u/3380730?v=4"},"body":"On 27.06.2018 21:11, Junio C Hamano wrote:\n> Marc Strapetz writes:\n> \n>> [1. text/plain]\n>> The current description of \"core.ignoreCase\" reads like an option which\n>> is intended to be changed by the user while it's actually expected to\n>> be set by Git on initialization only. Subsequently, Git relies on the\n>> proper configuration of this variable, as noted by Bryan Turner [1]:\n>>\n>> Git on a case-insensitive filesystem (APFS, HFS+, FAT32, exFAT,\n>> vFAT, NTFS, etc.) is not designed to be run with anything other\n>> than core.ignoreCase=true.\n>>\n>> [1] https://marc.info/?l=git&m=152998665813997&w=2\n>> mid:CAGyf7-GeE8jRGPkME9rHKPtHEQ6P1+ebpMMWAtMh01uO3bfy8w@mail.gmail.com\n>>\n>> Signed-off-by: Marc Strapetz \n>> ---\n>> Documentation/config.txt | 9 ++++++---\n>> 1 file changed, 6 insertions(+), 3 deletions(-)\n>>\n> \n> Hmph. Do other people have difficulty applying this patch to their\n> trees? It is just several lines long so I could retype it myself,\n> but I guess \"Content-Type: text/plain; charset=utf-8; format=flowed\"\n> has destroyed formatting of the patch rather badly.\n\nI had copy-pasted the patch into Thunderbird. The received email was \nlooking fine in the inbox, however it seems that some leading \nwhitespaces have been added to several lines (when comparing raw \ncontents of v3 and v4). I have resent the patch with git send-email now.\n\n-Marc\n"},{"id":"351235","messageId":"xmqqmuveyi1r.fsf@gitster-ct.c.googlers.com","threadId":"48771","inReplyTo":"20180628112157.17176-1-marc.strapetz@syntevo.com","subject":"Re: [PATCH v4] Documentation: declare \"core.ignoreCase\" as internal variable","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-06-28T16:47:28Z","receivedAt":"2018-06-28T16:47:33Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks.\n"},{"id":"351238","messageId":"752f02f7-71e7-9026-9894-d4572b65b187@web.de","threadId":"48771","inReplyTo":"20180628112157.17176-1-marc.strapetz@syntevo.com","subject":"Re: [PATCH v4] Documentation: declare \"core.ignoreCase\" as internal variable","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2018-06-28T16:58:26Z","receivedAt":"2018-06-28T17:03:53Z","isPatch":true,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On 28.06.18 13:21, Marc Strapetz wrote:\n> The current description of \"core.ignoreCase\" reads like an option which\n> is intended to be changed by the user while it's actually expected to\n> be set by Git on initialization only. Subsequently, Git relies on the\n> proper configuration of this variable, as noted by Bryan Turner [1]:\n> \n> Git on a case-insensitive filesystem (APFS, HFS+, FAT32, exFAT,\n> vFAT, NTFS, etc.) is not designed to be run with anything other\n> than core.ignoreCase=true.\n> \n> [1] https://marc.info/?l=git&m=152998665813997&w=2\n> mid:CAGyf7-GeE8jRGPkME9rHKPtHEQ6P1+ebpMMWAtMh01uO3bfy8w@mail.gmail.com\n> \n> Signed-off-by: Marc Strapetz \n> ---\n> Documentation/config.txt | 9 ++++++---\n> 1 file changed, 6 insertions(+), 3 deletions(-)\n> \n> diff --git a/Documentation/config.txt b/Documentation/config.txt\n> index 1cc18a828..c70cfe956 100644\n> --- a/Documentation/config.txt\n> +++ b/Documentation/config.txt\n> @@ -390,16 +390,19 @@ core.hideDotFiles::\n> \tdefault mode is 'dotGitOnly'.\n> \n> core.ignoreCase::\n> -\tIf true, this option enables various workarounds to enable\n> +\tInternal variable which enables various workarounds to enable\n> \tGit to work better on filesystems that are not case sensitive,\n> -\tlike FAT. For example, if a directory listing finds\n> -\t\"makefile\" when Git expects \"Makefile\", Git will assume\n> +\tlike APFS, HFS+, FAT, NTFS, etc. For example, if a directory listing\n> +\tfinds \"makefile\" when Git expects \"Makefile\", Git will assume\n> \tit is really the same file, and continue to remember it as\n> \t\"Makefile\".\n> +\n> The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n> will probe and set core.ignoreCase true if appropriate when the repository\n> is created.\n> ++\n> +Git relies on the proper configuration of this variable for your operating\n> +and file system. Modifying this value may result in unexpected behavior.\n> \n> core.precomposeUnicode::\n> \tThis option is only used by Mac OS implementation of Git.\n> \n\nLooks good to me\n"}]}