Re: Bug with line endings on git.

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

 



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.)





[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]

  Powered by Linux