{"thread":{"id":"49224","subject":"Automatic core.autocrlf?","startedAt":"2018-08-27T14:10:48Z","lastAt":"2018-08-31T13:17:17Z","messageCount":15,"participants":["Robert Dailey","Torsten Bögershausen","Duy Nguyen","Andrei Rybak","brian m. carlson","Jonathan Nieder","Randall S. Becker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"356581","messageId":"CAHd499APYCH2r2=+M_AGKUzN0GDmrwDty4wK=Xy-utCdMrd56w@mail.gmail.com","threadId":"49224","inReplyTo":null,"subject":"Automatic core.autocrlf?","fromName":"Robert Dailey","fromEmail":"rcdailey.lists@gmail.com","sentAt":"2018-08-27T14:10:33Z","receivedAt":"2018-08-27T14:10:48Z","isPatch":false,"sender":{"key":"rcdailey.lists@gmail.com","avatar":null},"body":"Is there an 'auto' setting for the 'core.autocrlf' config? Reason I\nask is, I want that setting to be 'input' on linux but 'true' on\nWindows. I have a global .gitconfig that I sync across different\nplatforms with Google Drive, and I hate to manage 2 copies of it on\neach platform (linux and Windows). If there's some way to make the\nline ending configuration the same between both, that would be\nawesome.\n\nNote that I do rely mostly on git attributes files for this, however\nnot all upstream repositories have one, and I don't always have\npermission to create one there. In those cases, when it falls back to\nconfiguration for line ending management, I want it to be\nautomatically configured based on the host platform.\n\nAny advice is appreciated here. Unfortunately Google isn't much help\non this topic, Stack Overflow is a swamp full of different information\nand none of it seems authoritative.\n"},{"id":"356585","messageId":"20180827153524.GA18025@tor.lan","threadId":"49224","inReplyTo":"CAHd499APYCH2r2=+M_AGKUzN0GDmrwDty4wK=Xy-utCdMrd56w@mail.gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2018-08-27T15:35:24Z","receivedAt":"2018-08-27T15:35:27Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Mon, Aug 27, 2018 at 09:10:33AM -0500, Robert Dailey wrote:\n> Is there an 'auto' setting for the 'core.autocrlf' config? Reason I\n> ask is, I want that setting to be 'input' on linux but 'true' on\n> Windows. I have a global .gitconfig that I sync across different\n> platforms with Google Drive, and I hate to manage 2 copies of it on\n> each platform (linux and Windows). If there's some way to make the\n> line ending configuration the same between both, that would be\n> awesome.\n> \n> Note that I do rely mostly on git attributes files for this, however\n> not all upstream repositories have one, and I don't always have\n> permission to create one there.\n\nHow many repos do you look at, and how big is the \"pain level\" here?\nWould it be possible to submit pull-requests ?\n\n> In those cases, when it falls back to\n> configuration for line ending management, I want it to be\n> automatically configured based on the host platform.\n\nThere is\ngit config core.eol native\n\nBut that is already the default, and it needs the 'text' attribute\nto be set (or auto), the simplest solution is to have\n* text=auto\nin .gitattributes\n\n> \n> Any advice is appreciated here. Unfortunately Google isn't much help\n> on this topic, Stack Overflow is a swamp full of different information\n> and none of it seems authoritative.\n\n\nOut of interest, not to blame anybody:\nDid you ever look at\n\nhttps://git-scm.com/docs/git-config\n\nThe authoritative answer is in the Git project itself,\nunder Documentation/config.txt\n\nIn summary, if I understand you right,\nthe solution would be to use .gitattributes in every project.\n\nHTH\n\n"},{"id":"356586","messageId":"CACsJy8Bik2Hokgv46ifsFhhvGzdcB=FoWnWs6_k2361s15wOPA@mail.gmail.com","threadId":"49224","inReplyTo":"20180827153524.GA18025@tor.lan","subject":"Re: Automatic core.autocrlf?","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2018-08-27T15:52:44Z","receivedAt":"2018-08-27T15:53:13Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Aug 27, 2018 at 5:37 PM Torsten Bögershausen wrote:\n> > In those cases, when it falls back to\n> > configuration for line ending management, I want it to be\n> > automatically configured based on the host platform.\n>\n> There is\n> git config core.eol native\n\nAn alternative is supporting conditional config includes based on\nplatform or host name, but I don't know if there are more use cases\nlike this to justify it.\n-- \nDuy\n"},{"id":"356590","messageId":"CAHd499AFUtW3=JNrmevdHRLgfK+QSdpkkSj0wsbRkhE8tqu-rA@mail.gmail.com","threadId":"49224","inReplyTo":"CACsJy8Bik2Hokgv46ifsFhhvGzdcB=FoWnWs6_k2361s15wOPA@mail.gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Robert Dailey","fromEmail":"rcdailey.lists@gmail.com","sentAt":"2018-08-27T17:29:12Z","receivedAt":"2018-08-27T17:29:27Z","isPatch":false,"sender":{"key":"rcdailey.lists@gmail.com","avatar":null},"body":"On Mon, Aug 27, 2018 at 10:53 AM Duy Nguyen wrote:\n>\n> On Mon, Aug 27, 2018 at 5:37 PM Torsten Bögershausen wrote:\n> > > In those cases, when it falls back to\n> > > configuration for line ending management, I want it to be\n> > > automatically configured based on the host platform.\n> >\n> > There is\n> > git config core.eol native\n>\n> An alternative is supporting conditional config includes based on\n> platform or host name, but I don't know if there are more use cases\n> like this to justify it.\n\nTo Torsten's comment: Yes, I've looked at git-config. it doesn't have\nthe answer to my question there, hence I posted on the mailing list.\nTo your point, eol being native doesn't matter if text=auto can't be\nsimulated. If there was a version of `autocrlf` that set `eol=native`\nand `text=auto`, that would work as well. But the `true` setting sets\n`text=auto` and `eol=crlf`.\n\nDuy: There are more use cases I've run into, but they are not related to the OP:\n\n* Different user email between machines (work vs personal)\n* Different tooling on platform (e.g. `nano` on Ubuntu, Notepad++ on Windows)\n\nCentralizing .gitconfig, especially when you have tons of aliases,\nbecomes more important. 95% of my .gitconfig is platform-agnostic, if\nthere was an `#ifdef` mechanism, per your suggestion, this would allow\na lot more flexibility. Maybe I should have worded my OP more in terms\nof platform-specific configuration sections, instead of specifically\nabout autocrlf, since that's just one symptom of the real problem.\n"},{"id":"356592","messageId":"94afe154-53e1-761a-4a66-4f77188036f7@gmail.com","threadId":"49224","inReplyTo":"CACsJy8Bik2Hokgv46ifsFhhvGzdcB=FoWnWs6_k2361s15wOPA@mail.gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Andrei Rybak","fromEmail":"rybak.a.v@gmail.com","sentAt":"2018-08-27T17:32:08Z","receivedAt":"2018-08-27T17:32:14Z","isPatch":false,"sender":{"key":"rybak.a.v@gmail.com","avatar":"https://avatars.githubusercontent.com/u/624072?v=4"},"body":"On 2018-08-27 17:52, Duy Nguyen wrote:\n> On Mon, Aug 27, 2018 at 5:37 PM Torsten Bögershausen wrote:\n>>> In those cases, when it falls back to\n>>> configuration for line ending management, I want it to be\n>>> automatically configured based on the host platform.\n>>\n> \n> An alternative is supporting conditional config includes based on\n> platform or host name, but I don't know if there are more use cases\n> like this to justify it.\n> \n\nHow about just using unconditional includes?\n\nglobal.gitconfig (synced across machines):\n\n [include]\n path = platform-specific.gitconfig\n\nAnd two version of file named \"platform-specific.gitconfig\", which\nare not synced, and include only code.autocrlf setting.\n\n--\nBest regards, Andrei R.\n"},{"id":"356598","messageId":"293f37cc-3978-125a-25e1-0baef35420be@gmail.com","threadId":"49224","inReplyTo":"94afe154-53e1-761a-4a66-4f77188036f7@gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Andrei Rybak","fromEmail":"rybak.a.v@gmail.com","sentAt":"2018-08-27T18:22:19Z","receivedAt":"2018-08-27T18:22:24Z","isPatch":false,"sender":{"key":"rybak.a.v@gmail.com","avatar":"https://avatars.githubusercontent.com/u/624072?v=4"},"body":"On 2018-08-27 19:32, Andrei Rybak wrote:\n> \n> How about just using unconditional includes?\n> \n> global.gitconfig (synced across machines):\n> \n> [include]\n> path = platform-specific.gitconfig\n> \n> And two version of file named \"platform-specific.gitconfig\", which\n> are not synced, and include only code.autocrlf setting.\n\nRobert, in this setup you might also want (just for convenience)\nto sync files \"platform1.gitconfig\" and \"platform2.gitconfig\", so\nthat they are available everywhere for editing and can be copied\ninto local version of platform-specific.gitconfig at any time.\n\n"},{"id":"356642","messageId":"20180828001403.GA432229@genre.crustytoothpaste.net","threadId":"49224","inReplyTo":"94afe154-53e1-761a-4a66-4f77188036f7@gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2018-08-28T00:14:03Z","receivedAt":"2018-08-28T00:14:12Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Mon, Aug 27, 2018 at 07:32:08PM +0200, Andrei Rybak wrote:\n> On 2018-08-27 17:52, Duy Nguyen wrote:\n> > On Mon, Aug 27, 2018 at 5:37 PM Torsten Bögershausen wrote:\n> >>> In those cases, when it falls back to\n> >>> configuration for line ending management, I want it to be\n> >>> automatically configured based on the host platform.\n> >>\n> > \n> > An alternative is supporting conditional config includes based on\n> > platform or host name, but I don't know if there are more use cases\n> > like this to justify it.\n> > \n> \n> How about just using unconditional includes?\n> \n> global.gitconfig (synced across machines):\n> \n> [include]\n> path = platform-specific.gitconfig\n> \n> And two version of file named \"platform-specific.gitconfig\", which\n> are not synced, and include only code.autocrlf setting.\n\nThere's actually a way to do this that works with older Git versions as\nwell: put global config in .gitconfig and per-system config in\n.config/git/config. Or you can use some sort of script (say, a\nMakefile) to install the proper values based on your system.\n-- \nbrian m. carlson: Houston, Texas, US\nOpenPGP: https://keybase.io/bk2204\n"},{"id":"356935","messageId":"20180830045407.GB140348@aiede.svl.corp.google.com","threadId":"49224","inReplyTo":"CAHd499APYCH2r2=+M_AGKUzN0GDmrwDty4wK=Xy-utCdMrd56w@mail.gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-08-30T04:54:07Z","receivedAt":"2018-08-30T04:54:11Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nRobert Dailey wrote:\n\n> Is there an 'auto' setting for the 'core.autocrlf' config? Reason I\n> ask is, I want that setting to be 'input' on linux but 'true' on\n> Windows.\n\nOthers are exploring your question about the configuration language,\nbut I want to emphasize some other ramifications.\n\nWhy do we still have 'core.autocrlf'? Do 'core.eol' and related\nsettings take care of that need, or is autocrlf still needed? If\ncore.eol etc do not take care of this need, what should we do to get\nthem to?\n\nThanks, after having run into a few too many autocrlf-related messes,\nJonathan\n"},{"id":"356980","messageId":"CAHd499AgNygMLiaLj=KSXDZJ8f3fAM60E9Pj=ADnc0POfrtKew@mail.gmail.com","threadId":"49224","inReplyTo":"94afe154-53e1-761a-4a66-4f77188036f7@gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Robert Dailey","fromEmail":"rcdailey.lists@gmail.com","sentAt":"2018-08-30T14:53:07Z","receivedAt":"2018-08-30T14:53:22Z","isPatch":false,"sender":{"key":"rcdailey.lists@gmail.com","avatar":null},"body":"On Mon, Aug 27, 2018 at 12:32 PM Andrei Rybak wrote:\n>\n> On 2018-08-27 17:52, Duy Nguyen wrote:\n> > On Mon, Aug 27, 2018 at 5:37 PM Torsten Bögershausen wrote:\n> >>> In those cases, when it falls back to\n> >>> configuration for line ending management, I want it to be\n> >>> automatically configured based on the host platform.\n> >>\n> >\n> > An alternative is supporting conditional config includes based on\n> > platform or host name, but I don't know if there are more use cases\n> > like this to justify it.\n> >\n>\n> How about just using unconditional includes?\n>\n> global.gitconfig (synced across machines):\n>\n> [include]\n> path = platform-specific.gitconfig\n>\n> And two version of file named \"platform-specific.gitconfig\", which\n> are not synced, and include only code.autocrlf setting.\n\nI think I tried this some years back, but ended up ditching it because\nwhen you modify settings via `git config --global`, it doesn't put\nvalues in the right files. This is probably the best answer so far\nthough. It would still be great to have a mechanism that works within\n1 file and is friendly to the git config command.\n"},{"id":"356981","messageId":"CAHd499BCk4Q4oPY=CXK=YrUbNUbz4J_KoeQngfz=92Qfc6q=eA@mail.gmail.com","threadId":"49224","inReplyTo":"20180830045407.GB140348@aiede.svl.corp.google.com","subject":"Re: Automatic core.autocrlf?","fromName":"Robert Dailey","fromEmail":"rcdailey.lists@gmail.com","sentAt":"2018-08-30T14:57:52Z","receivedAt":"2018-08-30T14:58:07Z","isPatch":false,"sender":{"key":"rcdailey.lists@gmail.com","avatar":null},"body":"On Wed, Aug 29, 2018 at 11:54 PM Jonathan Nieder wrote:\n>\n> Hi,\n>\n> Robert Dailey wrote:\n>\n> > Is there an 'auto' setting for the 'core.autocrlf' config? Reason I\n> > ask is, I want that setting to be 'input' on linux but 'true' on\n> > Windows.\n>\n> Others are exploring your question about the configuration language,\n> but I want to emphasize some other ramifications.\n>\n> Why do we still have 'core.autocrlf'? Do 'core.eol' and related\n> settings take care of that need, or is autocrlf still needed? If\n> core.eol etc do not take care of this need, what should we do to get\n> them to?\n>\n> Thanks, after having run into a few too many autocrlf-related messes,\n> Jonathan\n\nFrom my perspective, the confusion is due to the evolution of the\nfeature. There's multiple ways to control EOL handling but most of it\nis legacy/backward compatibility, I think. core.autocrlf is a\nfall-back for repos that do not have a .gitattributes. Because\n.gitattributes is optional by design, I'm not sure if getting rid of\nthe config options is a good idea. But your point did make me think\nabout how `core.autocrlf = true` should probably be a system config\ndefault for the Git for Windows project. The default for that value\nshould be platform-defined. That would make it automatically work the\nway I want, and might solve a lot of the issues where people are\ncommitting CRLF into repositories on Windows.\n"},{"id":"357000","messageId":"20180830185648.GA10427@tor.lan","threadId":"49224","inReplyTo":"CAHd499BCk4Q4oPY=CXK=YrUbNUbz4J_KoeQngfz=92Qfc6q=eA@mail.gmail.com","subject":"Re: Automatic core.autocrlf?","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2018-08-30T18:56:48Z","receivedAt":"2018-08-30T18:56:52Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Thu, Aug 30, 2018 at 09:57:52AM -0500, Robert Dailey wrote:\n> On Wed, Aug 29, 2018 at 11:54 PM Jonathan Nieder wrote:\n> >\n> > Hi,\n> >\n> > Robert Dailey wrote:\n> >\n> > > Is there an 'auto' setting for the 'core.autocrlf' config? Reason I\n> > > ask is, I want that setting to be 'input' on linux but 'true' on\n> > > Windows.\n> >\n> > Others are exploring your question about the configuration language,\n> > but I want to emphasize some other ramifications.\n> >\n> > Why do we still have 'core.autocrlf'? Do 'core.eol' and related\n> > settings take care of that need, or is autocrlf still needed? If\n> > core.eol etc do not take care of this need, what should we do to get\n> > them to?\n> >\n> > Thanks, after having run into a few too many autocrlf-related messes,\n> > Jonathan\n> \n> From my perspective, the confusion is due to the evolution of the\n> feature. There's multiple ways to control EOL handling but most of it\n> is legacy/backward compatibility, I think. core.autocrlf is a\n> fall-back for repos that do not have a .gitattributes. Because\n> .gitattributes is optional by design, I'm not sure if getting rid of\n> the config options is a good idea.\n\nGood summary. My original plan was to try to \"make obsolete\"/retire\nand phase out core.autocrlf completely.\nHowever, since e.g. egit/jgit uses it\n(they don't have support for .gitattributes at all) I am not sure if this\nis a good idea either. Opinions are welcome.\n\n\n> But your point did make me think\n> about how `core.autocrlf = true` should probably be a system config\n> default for the Git for Windows project. The default for that value\n> should be platform-defined. That would make it automatically work the\n> way I want, and might solve a lot of the issues where people are\n> committing CRLF into repositories on Windows.\n\nUnless I am wrong, that had been the default a long time ago:\nGit for Windows (at that time msysgit) had core.autocrlf=true\nby default.\nWhile this is a good choice for many repos, some people prefer\ncore.autocrlf=input.\nOthers just commit files for Windows-based repos with CRLF,\nand the advantage is, that \"git diff\" doesn't show \"^M\" somewhere.\n\nI allways encourage people to set up a .gitattributes file.\nDoes anybody thinks that we can make core.autocrlf obsolete ?\n\n\n"},{"id":"357001","messageId":"005c01d44095$1d5288c0$57f79a40$@nexbridge.com","threadId":"49224","inReplyTo":"20180830185648.GA10427@tor.lan","subject":"RE: Automatic core.autocrlf?","fromName":"Randall S. Becker","fromEmail":"rsbecker@nexbridge.com","sentAt":"2018-08-30T19:10:23Z","receivedAt":"2018-08-30T19:10:37Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On August 30, 2018 2:57 PM, Torsten Bögershausen wrote:\n> On Thu, Aug 30, 2018 at 09:57:52AM -0500, Robert Dailey wrote:\n> > On Wed, Aug 29, 2018 at 11:54 PM Jonathan Nieder \n> wrote:\n> > >\n> > > Hi,\n> > >\n> > > Robert Dailey wrote:\n> > >\n> > > > Is there an 'auto' setting for the 'core.autocrlf' config? Reason\n> > > > I ask is, I want that setting to be 'input' on linux but 'true' on\n> > > > Windows.\n> > >\n> > > Others are exploring your question about the configuration language,\n> > > but I want to emphasize some other ramifications.\n> > >\n> > > Why do we still have 'core.autocrlf'? Do 'core.eol' and related\n> > > settings take care of that need, or is autocrlf still needed? If\n> > > core.eol etc do not take care of this need, what should we do to get\n> > > them to?\n> > >\n> > > Thanks, after having run into a few too many autocrlf-related\n> > > messes, Jonathan\n> >\n> > From my perspective, the confusion is due to the evolution of the\n> > feature. There's multiple ways to control EOL handling but most of it\n> > is legacy/backward compatibility, I think. core.autocrlf is a\n> > fall-back for repos that do not have a .gitattributes. Because\n> > .gitattributes is optional by design, I'm not sure if getting rid of\n> > the config options is a good idea.\n> \n> Good summary. My original plan was to try to \"make obsolete\"/retire and\n> phase out core.autocrlf completely.\n> However, since e.g. egit/jgit uses it\n> (they don't have support for .gitattributes at all) I am not sure if this\nis a good\n> idea either. Opinions are welcome.\n> \n> \n> > But your point did make me think\n> > about how `core.autocrlf = true` should probably be a system config\n> > default for the Git for Windows project. The default for that value\n> > should be platform-defined. That would make it automatically work the\n> > way I want, and might solve a lot of the issues where people are\n> > committing CRLF into repositories on Windows.\n> \n> Unless I am wrong, that had been the default a long time ago:\n> Git for Windows (at that time msysgit) had core.autocrlf=true by default.\n> While this is a good choice for many repos, some people prefer\n> core.autocrlf=input.\n> Others just commit files for Windows-based repos with CRLF, and the\n> advantage is, that \"git diff\" doesn't show \"^M\" somewhere.\n> \n> I allways encourage people to set up a .gitattributes file.\n> Does anybody thinks that we can make core.autocrlf obsolete ?\n\nThe last time I checked, EGit does not set this by default. ECLIPSE Oxygen\n3A/EGit-JGit 5.0.1, when running on Windows, creates core.filemode=false,\ncore.logallrefupdates=true, repositoryformatversion=0, symlinks=false. Some\nSourceTree versions that predate the newer SourceTreeApp are somewhat stuck\non older embedded versions of git, but that may not be relevant. Personally,\nI would seriously like to drop core.autocrlf and just have everyone on LF\nEOL characters. I get frequently burnt by this despite knowing better.\n\nCheers,\nRandall\n\n-- Brief whoami:\n NonStop developer since approximately 211288444200000000\n UNIX developer since approximately 421664400\n-- In my real life, I talk too much.\n\n\n\n"},{"id":"357061","messageId":"20180831032917.GC98946@aiede.svl.corp.google.com","threadId":"49224","inReplyTo":"20180830185648.GA10427@tor.lan","subject":"Re: Automatic core.autocrlf?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-08-31T03:29:17Z","receivedAt":"2018-08-31T03:29:46Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nTorsten Bögershausen wrote:\n\n> My original plan was to try to \"make obsolete\"/retire\n> and phase out core.autocrlf completely.\n> However, since e.g. egit/jgit uses it\n> (they don't have support for .gitattributes at all) I am not sure if this\n> is a good idea either.\n\nInteresting. [1] appears to have intended to add this feature.\nDo you remember when it is that you tested?\n\nFeel free to file bugs using [2] for any missing features.\n\nThanks,\nJonathan\n\n[1] https://git.eclipse.org/r/c/60635\n[2] https://www.eclipse.org/jgit/support/\n"},{"id":"357083","messageId":"000c01d44121$bf563090$3e0291b0$@nexbridge.com","threadId":"49224","inReplyTo":"20180831032917.GC98946@aiede.svl.corp.google.com","subject":"RE: Automatic core.autocrlf?","fromName":"Randall S. Becker","fromEmail":"rsbecker@nexbridge.com","sentAt":"2018-08-31T11:57:04Z","receivedAt":"2018-08-31T11:57:16Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"\nOn August 30, 2018 11:29 PM, Jonathan Nieder wrote:\n> Torsten Bögershausen wrote:\n> \n> > My original plan was to try to \"make obsolete\"/retire and phase out\n> > core.autocrlf completely.\n> > However, since e.g. egit/jgit uses it\n> > (they don't have support for .gitattributes at all) I am not sure if\n> > this is a good idea either.\n> \n> Interesting. [1] appears to have intended to add this feature.\n> Do you remember when it is that you tested?\n> \n> Feel free to file bugs using [2] for any missing features.\n> \n> [1] https://git.eclipse.org/r/c/60635\n> [2] https://www.eclipse.org/jgit/support/\n\nMy testing was done on EGit 5.0.1 yesterday, which does not provide a default to core.autocrlf.\n\nCheers,\nRandall\n\n"},{"id":"357085","messageId":"20180831131703.GA20800@tor.lan","threadId":"49224","inReplyTo":"000c01d44121$bf563090$3e0291b0$@nexbridge.com","subject":"Re: Automatic core.autocrlf?","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2018-08-31T13:17:03Z","receivedAt":"2018-08-31T13:17:17Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Fri, Aug 31, 2018 at 07:57:04AM -0400, Randall S. Becker wrote:\n> \n> On August 30, 2018 11:29 PM, Jonathan Nieder wrote:\n> > Torsten Bögershausen wrote:\n> > \n> > > My original plan was to try to \"make obsolete\"/retire and phase out\n> > > core.autocrlf completely.\n> > > However, since e.g. egit/jgit uses it\n> > > (they don't have support for .gitattributes at all) I am not sure if\n> > > this is a good idea either.\n> > \n> > Interesting. [1] appears to have intended to add this feature.\n> > Do you remember when it is that you tested?\n> > \n> > Feel free to file bugs using [2] for any missing features.\n> > \n> > [1] https://git.eclipse.org/r/c/60635\n> > [2] https://www.eclipse.org/jgit/support/\n\nOh, (I thought that I digged into the source recently...)\nThanks for the clarification\n\n> \n> My testing was done on EGit 5.0.1 yesterday, which does not provide a default to core.autocrlf.\n> \n> Cheers,\n> Randall\n> \n\nOK, then I assume that jgit supports .gitattributes now.\nJust to ask a possibly stupid question: did anybody test it ?\n\n"}]}