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

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

From
Yann Droneaud <ydroneaud@opteya.com>
Date
Jun 24, 2013, 16:43 UTC
Message-ID
<a52e61e60f626e8ad75435af94a85042@meuh.org>
In-Reply-To
<866f886ef5e48ba22eec0f67203666bb@meuh.org>
Le 24.06.2013 18:37, Yann Droneaud a écrit :
Show 7 quoted lines
> I'm still trying to use .gitattributes "text" flag with CRLF line 
> ending files
> under Linux.
> 
> I'm surprised about the interaction between the index and the working 
> directory,
> more specificaly about the interaction between git diff and git status:
[...]
Show 7 quoted lines
> - Why git diff does not always report the CRLF/LF mismatch ?
> 
> - Why git status does not report about the CRLF/LF mismatch before
> updating the index:
>   it silently hide the CRLF/LF warning.
>   git add, git commit report the warning. git status should probably
> do the same.

Can this problem be related to the rebase failure I've described in thread "git rebase fail with CRLF conversion" [1][2][3] ?

1. <fb20a7d711fdd218f58f1f2090b1c515@meuh.org>
2. <http://thread.gmane.org/gmane.comp.version-control.git/228613>
3. <http://marc.info/?l=git&m=137182211414404&w=2>
Regards.
-- 
Yann Droneaud
OPTEYA
Previous: Yann DroneaudNext: Junio C Hamano
Message 2 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.