Re: What should be the CRLF policy when win + Linux?

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

 



In message <o2v40aa078e1005061625md5fede79h660a22227c4f22d1@xxxxxxxxxxxxxx>, Erik Faye-Lund <kusmabite@xxxxxxxxxxxxxx> writes
Closed source does not imply a single operating system, and you get
these issues whenever you have a project with targets systems with
different newline style. In my day job I develop closed source,
multi-platform software, using git. So it's certainly not MY most
common scenario.

And there's a lot more line endings out there than just lf or crlf.

Okay, the two I'm about to quote have, I believe, gone the way of the dinosaur, but wasn't the mac just cr? And what is *still* my favourite system, Prime (a multics derivative too), used a "packed lf", so your line ending could be either lf or lfnull depending on the line length (it was always stored on disk as an integral word-length, a word being 16 bits. So if your text was an even number of characters, the ending was lfnull to pad it to the next word boundary).

Cheers,
Wol
--
Anthony W. Youngman - anthony@xxxxxxxxxxxxxxxxxxxxx

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