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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le 24.06.2013 18:37, Yann Droneaud a écrit :

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:

[...]

- 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@xxxxxxxx>
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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]