From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: "Benkstein\, Frank" <frank.benkstein@sap.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git blame breaking on repository with CRLF files
Date: Mon, 10 Aug 2015 11:48:35 -0700 [thread overview]
Message-ID: <xmqq1tfbugho.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <55C7B5EE.7060908@web.de> ("Torsten Bögershausen"'s message of "Sun, 9 Aug 2015 22:19:58 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> Actually I could reproduce the following:
> CRLF in repo, CRLF in working tree, core.autocrlf= true.
What should happen in such a case? Wouldn't autocrlf=true want to
strip CRLF down to LF? Shouldn't it? And if so, "blame" is correct
to say that you are changing the line endings of all your lines, as
what you _would_ commit if you were to commit the tracked files in
your working tree would be different from what is in the index, no?
next prev parent reply other threads:[~2015-08-10 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 16:32 git blame breaking on repository with CRLF files Benkstein, Frank
2015-08-08 5:58 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1tfbugho.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=frank.benkstein@sap.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.