Re: CRLF problems with Git on Win32

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

 



On Jan 10, 2008 8:28 AM, Peter Karlsson <peter@xxxxxxxxxxxxxxxx> wrote:
> I meant to say that any software that claims to be Windows software
> should handle, and produce, CRLF line breaks in text files.

Including zip/unzip? How about tar? rsync? NFS and SMB copies from
network shares? I bet the Samba folks would just *love* to have this
discussion for the hundredth time.

Just because CVS and FTP got the defaults wrong (and modern FTP
clients mostly default to automatically switching to binary, so
basically just CVS) doesn't mean that Git has to get the default
wrong, too. Git *does* handle and produce CRLF line breaks, as long as
you tell it to. Please don't lose sight of that fact.

I'm just glad that VMS is effectively dead. Line endings on VMS are
stored outside the text body, IIRC...

Peter Harris
-
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]

  Powered by Linux