git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Benkstein, Frank" <frank.benkstein@sap.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: git blame breaking on repository with CRLF files
Date: Fri, 7 Aug 2015 16:32:58 +0000	[thread overview]
Message-ID: <B0BFE3BB9B3E8C4A890D53FA460552D3737328B0@DEWDFEMB16B.global.corp.sap> (raw)

Hello,

I am working working on Linux and am examining code in a git repository I do
not know much about.  I am only looking at files, not changing anything.  On
some files in the repository I get "00000000 (Not Committed Yet" for all lines
when running "git blame".  I checked with "git status", "git reset", "git
clean" that the files are indeed in the repository and unmodified.  I noticed
that this only happens with git v2.5.0.  With git v2.4.0 it looks correct, i.e.
the output has proper commit ids, Author names and dates..  With "git bisect" I
tracked this down to the following commit:

 commit 4bf256d67a85bed1e175ecc2706322eafe4489ca (HEAD, refs/bisect/bad)
 Author: Torsten Bögershausen <tboegi@web.de>
 Date:   Sun May 3 18:38:01 2015 +0200

     blame: CRLF in the working tree and LF in the repo

Digging further, it seems that most files in the repository are checked in with
CRLF line endings.  In my working tree these are checked out as LF - which
seems to be the exact opposite situation of what the commit is trying to
address.  When I set "core.autocrlf" to "false" I also get the correct behavior
of "git blame" - this is a workaround as long as I do not have to actually
modify anything.

Best regards,
Frank.

             reply	other threads:[~2015-08-07 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 16:32 Benkstein, Frank [this message]
2015-08-08  5:58 ` git blame breaking on repository with CRLF files Torsten Bögershausen
2015-08-09 20:19   ` Torsten Bögershausen
2015-08-10  8:36     ` Benkstein, Frank
2015-08-10 23:54       ` brian m. carlson
2015-08-10 18:48     ` Junio C Hamano
2015-08-10 20:22       ` Torsten Bögershausen

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=B0BFE3BB9B3E8C4A890D53FA460552D3737328B0@DEWDFEMB16B.global.corp.sap \
    --to=frank.benkstein@sap.com \
    --cc=git@vger.kernel.org \
    /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).