git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: PugzAreCute <me@pugzarecute.com>
To: Torsten =?unknown-8bit?Q?B=C3=B6gershausen?= <tboegi@web.de>
Cc: "git" <git@vger.kernel.org>
Subject: Re: Bug with line endings on git.
Date: Tue, 31 Aug 2021 08:11:28 +0530	[thread overview]
Message-ID: <17b9a153d45.50a7d553139551.115021994511161928@pugzarecute.com> (raw)
In-Reply-To: <20210830191712.4nufzooxfoyuh5yc@tb-raspi4>

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@web.de> 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.) 
 >  


      reply	other threads:[~2021-08-31  2:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 17:50 Bug with line endings on git PugzAreCute
2021-08-30 19:17 ` Torsten =?unknown-8bit?Q?B=C3=B6gershausen?=
2021-08-31  2:41   ` PugzAreCute [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17b9a153d45.50a7d553139551.115021994511161928@pugzarecute.com \
    --to=me@pugzarecute.com \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).