Using Debian 11 (amd64) The only thing that was changed in the comments were the line endings. ie: CRLF to LF and vice versa I can confirm this is only effecting installs with autocrlf disabled. On my local machine, I have enabled autocrlf and I cannot reproduce the bug. But if you want to test it, you could use https://github.dev/ as it has autocrlf disabled. Ouptput of git config --get core.autocrlf: pugzarecute@debinax:~$ git config --get core.autocrlf input Thanks, PugzAreCute ---- On Tue, 31 Aug 2021 00:47:12 +0530 Torsten =?unknown-8bit?Q?B=C3=B6gershausen?= <tboegi@xxxxxx> wrote ---- > On Mon, Aug 30, 2021 at 11:20:18PM +0530, PugzAreCute wrote: > > Hello, > > I want to report a bug with git that causes "empty" commits if the line ending of a file is changed. > > > > For example: https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece.patch (patch) / https://github.com/PugzAreCute/RFOEC/commit/31f5189cac3e076252372d634708b875a364dece (commit) > > > > First seen by me on https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283 / https://github.com/PugsMods/WoneWay/commit/fe58a091498eb5d891e351dba0273fd8e6d4d283.patch > > > > > > Happy to provide more info! > > More info would be appreciated. > Are you working under Windows ? > > Both commits (31f5189cac3e076252372d634708b875a364dece and > be50904c84b56926f9f7f9912af6456edab82ca1) have the same content: > > git ls-files -s > > 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 COMMIT > 100644 0eb95c07f7dd518679684826ff9ea516010c3847 0 README.md > > So what exactly did you change ? > The line endings in the working tree ? > What does > git config --get core.autocrlf > give you ? > > > > > Thanks, > > PugzAreCute(Murali H.) >
