Re: [PATCH/RFC] blame: CRLF in the working tree and LF in the repo
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Apr 28, 2015, 20:19 UTC
- Message-ID
- <553FEB4F.7050409@kdbg.org>
- In-Reply-To
- <xmqq7fswuj1s.fsf@gitster.dls.corp.google.com>
Am 28.04.2015 um 21:52 schrieb Junio C Hamano:
Show 9 quoted lines
> Johannes Sixt <j6t@kdbg.org> writes: > >> I set none of these. But I do commit CRLF and expect to get CRLF >> back. Am I commiting binary files? Am I doing something that "Git does >> not support"? Am I "on [my] own"? > > I think these specific sentences are merely uninformed opinions; if > I ignore and re-read what people said in the discussion, I think the > thread as a whole makes sense.
Thanks for the clarification. Following the thread only superficially, I feared some behavior change (or even just a redefinition of what "is supported") is about to surface that impacts established workflows.
-- Hannes