+ [2015-09-20T21:10:55Z] ToApolytoXaos greetings everyone. I don't know what's happening with github's search mechanism lately, but lots of nonsense pop up randomly; https://github.com/mozilla/rhino/search?l=cpp
+ [2015-09-20T21:12:15Z] ToApolytoXaos so the searching mechanism parses the first line and finds the following line "/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*- */" and considers it as a valid C++ file? :/
+ [2015-09-20T23:29:54Z] Terabyte ending conversion)...
+ [2015-09-20T23:29:54Z] Terabyte hey. I have set * text eol=LF yet a file called control which contains text and a file called schema.conf both came in after being freshly checked out with windows line endings... trying to them in with github for windows they showed up, then on hitting commit it said there was an error, then clicking another repo and coming back showed no files had changed (even though I had made a line
+ [2015-09-20T23:30:15Z] Terabyte what do I need to do to get these files committed with linux line endings..

message no. 112946

Posted by Terabyte in #github at 2015-09-20T23:29:54Z

hey. I have set * text eol=LF yet a file called control which contains text and a file called schema.conf both came in after being freshly checked out with windows line endings... trying to them in with github for windows they showed up, then on hitting commit it said there was an error, then clicking another repo and coming back showed no files had changed (even though I had made a line
+ [2015-09-21T08:21:17Z] nikC94 hello?
+ [2015-09-21T12:16:28Z] ronny hi
+ [2015-09-21T12:17:13Z] ronny anyone aware of a good worflow to make non-core contributors rebase their changes to a maintenance/bugfix branch in some cases?