On 6/17/2016 5:33 PM, Scott Robison wrote:
On Fri, Jun 17, 2016 at 6:04 PM, Warren Young <w...@etr-usa.com <mailto:w...@etr-usa.com>> wrote: .... For any blob data that Fossil considers “text,” why not strip all CRs on ingest, then based on either a setting or platform check inject CRs as necessary when expelling a copy from the DB? Then users checking out on Windows will see the CRLFs they want, and Fossil doesn’t have to deal with CRs appearing and disappearing as different users on different platforms edit the same files? Ah. I was just thinking for the text that fossil itself injects, not something that would impact all blobs. I wouldn't be opposed to that myself, but I can appreciate why it isn't a desirable thing for fossil to do.
IMHO, I think that one of fossil's strong points is that it is remarkably unaware of text vs. binary issues. Storing all files byte for byte as they are in the file system is a reflection of that. So is being agnostic about line ending when implementing text presentation features such as diff.
For text that is the property of fossil itself, such as checkin comments, it is completely fair and reasonable for it to pick a preferred line ending and convert to it from entry and from it on display.
-- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
