git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Another core.safecrlf behavor with git diff/git status

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 24, 2013, 16:55 UTC
Message-ID
<7v7ghjbg8i.fsf@alter.siamese.dyndns.org>
In-Reply-To
<866f886ef5e48ba22eec0f67203666bb@meuh.org>
Yann Droneaud <ydroneaud@opteya.com> writes:
> - Why git diff does not always report the CRLF/LF mismatch ?

Most likely because you are telling safecrlf not to error out but just warn, and then you are not fixing the cause of the warning? So diff would say "Ok, you must know what you are doing, so I trust what is in the index", perhaps?

> - Why git status does not report about the CRLF/LF mismatch before
> updating the index:
My suspicion is the same as "diff".
Previous: Yann DroneaudNext: Yann Droneaud
Message 3 of 5 in “Another core.safecrlf behavor with git diff/git status”
  1. Yann DroneaudJun 24, 2013
  2. Yann DroneaudJun 24, 2013
  3. Junio C HamanoJun 24, 2013
  4. Yann DroneaudJun 25, 2013
  5. Yann DroneaudJun 24, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.