{"thread":{"id":"56408","subject":"Bug with line endings on git.","startedAt":"2021-08-30T17:50:26Z","lastAt":"2021-08-31T02:41:37Z","messageCount":3,"participants":["PugzAreCute","Torsten B��gershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"434133","messageId":"17b982ef1f2.b8f13d4136798.2688982303431691937@pugzarecute.com","threadId":"56408","inReplyTo":null,"subject":"Bug with line endings on git.","fromName":"PugzAreCute","fromEmail":"me@pugzarecute.com","sentAt":"2021-08-30T17:50:18Z","receivedAt":"2021-08-30T17:50:26Z","isPatch":false,"sender":{"key":"me@pugzarecute.com","avatar":null},"body":"Hello, \nI want to report a bug with git that causes \"empty\" commits if the line ending of a file is changed.\n\nFor example: https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece.patch (patch) / https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece (commit)\n\nFirst seen by me on https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283 / https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283.patch\n\n\nHappy to provide more info!\n\nThanks, \nPugzAreCute(Murali H.)\n\n\n\n"},{"id":"434148","messageId":"20210830191712.4nufzooxfoyuh5yc@tb-raspi4","threadId":"56408","inReplyTo":"17b982ef1f2.b8f13d4136798.2688982303431691937@pugzarecute.com","subject":"Re: Bug with line endings on git.","fromName":"Torsten B��gershausen","fromEmail":"tboegi@web.de","sentAt":"2021-08-30T19:17:12Z","receivedAt":"2021-08-30T19:17:19Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Mon, Aug 30, 2021 at 11:20:18PM +0530, PugzAreCute wrote:\n> Hello,\n> I want to report a bug with git that causes \"empty\" commits if the line ending of a file is changed.\n>\n> For example: https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece.patch (patch) / https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece (commit)\n>\n> First seen by me on https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283 / https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283.patch\n>\n>\n> Happy to provide more info!\n\nMore info would be appreciated.\nAre you working under Windows ?\n\nBoth commits (31f5189cac3e076252372d634708b875a364dece and\nbe50904c84b56926f9f7f9912af6456edab82ca1) have the same content:\n\ngit ls-files -s\n\n100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0       COMMIT\n100644 0eb95c07f7dd518679684826ff9ea516010c3847 0       README.md\n\nSo what exactly did you change ?\nThe line endings in the working tree ?\nWhat does\ngit config --get  core.autocrlf\ngive you ?\n\n>\n> Thanks,\n> PugzAreCute(Murali H.)\n\n"},{"id":"434225","messageId":"17b9a153d45.50a7d553139551.115021994511161928@pugzarecute.com","threadId":"56408","inReplyTo":"20210830191712.4nufzooxfoyuh5yc@tb-raspi4","subject":"Re: Bug with line endings on git.","fromName":"PugzAreCute","fromEmail":"me@pugzarecute.com","sentAt":"2021-08-31T02:41:28Z","receivedAt":"2021-08-31T02:41:37Z","isPatch":false,"sender":{"key":"me@pugzarecute.com","avatar":null},"body":"Using Debian 11 (amd64)\nThe only thing that was changed in the comments were the line endings. ie: CRLF to LF and vice versa\n\nI can confirm this is only effecting installs with autocrlf disabled. On my local machine, I have enabled autocrlf and I cannot reproduce the bug.\nBut if you want to test it, you could use https://github.dev/ as it has autocrlf disabled.\n\nOuptput of git config --get core.autocrlf:\npugzarecute@debinax:~$ git config --get core.autocrlf\ninput\n\nThanks,\nPugzAreCute\n---- On Tue, 31 Aug 2021 00:47:12 +0530 Torsten =?unknown-8bit?Q?B=C3=B6gershausen?= <tboegi@web.de> wrote ----\n\n > On Mon, Aug 30, 2021 at 11:20:18PM +0530, PugzAreCute wrote: \n > > Hello, \n > > I want to report a bug with git that causes \"empty\" commits if the line ending of a file is changed. \n > > \n > > For example: https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece.patch (patch) / https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece (commit) \n > > \n > > First seen by me on https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283 / https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283.patch \n > > \n > > \n > > Happy to provide more info! \n >  \n > More info would be appreciated. \n > Are you working under Windows ? \n >  \n > Both commits (31f5189cac3e076252372d634708b875a364dece and \n > be50904c84b56926f9f7f9912af6456edab82ca1) have the same content: \n >  \n > git ls-files -s \n >  \n > 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0       COMMIT \n > 100644 0eb95c07f7dd518679684826ff9ea516010c3847 0       README.md \n >  \n > So what exactly did you change ? \n > The line endings in the working tree ? \n > What does \n > git config --get  core.autocrlf \n > give you ? \n >  \n > > \n > > Thanks, \n > > PugzAreCute(Murali H.) \n >  \n\n"}]}