{"thread":{"id":"4313","subject":"RE: [PATCH] Fixed Cygwin CR-munging problem in mailsplit","startedAt":"2006-05-27T20:57:35Z","lastAt":"2006-05-31T04:49:32Z","messageCount":3,"participants":["Zakirov, Salikh","Christopher Faylor","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"20813","messageId":"E124AAE027DA384D8B919F93E4D8C70801EFFB52@mssmsx402nb","threadId":"4313","inReplyTo":null,"subject":"RE: [PATCH] Fixed Cygwin CR-munging problem in mailsplit","fromName":"Zakirov, Salikh","fromEmail":"salikh.zakirov@intel.com","sentAt":"2006-05-27T20:57:35Z","receivedAt":"2006-05-27T20:57:35Z","isPatch":true,"sender":{"key":"salikh.zakirov@gmail.com","avatar":null},"body":"\nJunio C Hamano <junkio@cox.net> writes:\n> So even in this modern day, preserving CRLF is not\n> something that happens by default -- you would need to make sure\n> that everybody on your mailpath to the recipient is set up the\n> right way.\n\n> So now I am less in favor of the change than when I wrote that\n> response.\n\nI understand this reasoning, and I am not sure if the fix is correct\nfrom the \"GIT world\" point of view.\n\nHowever, I believe that the command sequence git-format-patch, git-am\nwithout any e-mail transfer in between and in the same repository\nshould work perfectly regardless of the contents of the files, \nno matter if they are binary, text, or \"CRLF text\" or even \n\"broken LF and CRLF text\". This is a requirement from a nasty \"real\nworld\".\n\nJunio, could you point at a right place to fix to get git-format-patch, \ngit-am sequence work flawlessly on Cygwin?\n\nBy the way, the change affects only non-Unix users, as fopen(..., \"rt\")\nis equivalent to fopen(..., \"rb\") on all Unixes anyway.\n"},{"id":"20823","messageId":"20060528163949.GB400@trixie.casa.cgf.cx","threadId":"4313","inReplyTo":"E124AAE027DA384D8B919F93E4D8C70801EFFB52@mssmsx402nb","subject":"Re: [PATCH] Fixed Cygwin CR-munging problem in mailsplit","fromName":"Christopher Faylor","fromEmail":"me@cgf.cx","sentAt":"2006-05-28T16:39:49Z","receivedAt":"2006-05-28T16:39:49Z","isPatch":true,"sender":{"key":"me@cgf.cx","avatar":null},"body":"On Sun, May 28, 2006 at 12:57:35AM +0400, Zakirov, Salikh wrote:\n>Junio C Hamano <junkio@cox.net> writes:\n>> So even in this modern day, preserving CRLF is not\n>> something that happens by default -- you would need to make sure\n>> that everybody on your mailpath to the recipient is set up the\n>> right way.\n>\n>> So now I am less in favor of the change than when I wrote that\n>> response.\n>\n>I understand this reasoning, and I am not sure if the fix is correct\n>from the \"GIT world\" point of view.\n>\n>However, I believe that the command sequence git-format-patch, git-am\n>without any e-mail transfer in between and in the same repository\n>should work perfectly regardless of the contents of the files, \n>no matter if they are binary, text, or \"CRLF text\" or even \n>\"broken LF and CRLF text\". This is a requirement from a nasty \"real\n>world\".\n>\n>Junio, could you point at a right place to fix to get git-format-patch, \n>git-am sequence work flawlessly on Cygwin?\n>\n>By the way, the change affects only non-Unix users, as fopen(..., \"rt\")\n>is equivalent to fopen(..., \"rb\") on all Unixes anyway.\n\nBut fopen(..., \"r\") is not equivalent to fopen(..., \"rb\") on Cygwin.\n\nWouldn't you want to add the \"b\" there to be assured of a binary open?\n\ncgf\n"},{"id":"20997","messageId":"7virnmyf1f.fsf@assigned-by-dhcp.cox.net","threadId":"4313","inReplyTo":"E124AAE027DA384D8B919F93E4D8C70801EFFB52@mssmsx402nb","subject":"Re: [PATCH] Fixed Cygwin CR-munging problem in mailsplit","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-05-31T04:49:32Z","receivedAt":"2006-05-31T04:49:32Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Zakirov, Salikh\" <salikh.zakirov@intel.com> writes:\n\n> However, I believe that the command sequence git-format-patch, git-am\n> without any e-mail transfer in between and in the same repository\n> should work perfectly regardless of the contents of the files, \n> no matter if they are binary, text, or \"CRLF text\" or even \n> \"broken LF and CRLF text\". This is a requirement from a nasty \"real\n> world\".\n\nOK, that's a very valid argument.  Thanks for straighten me out.\n"}]}