Interesting! I was unaware of the svn:eol-style property. However, I don't think git offers anything exactly like that..
This was all I could find on a search, which seems similar to what you are looking for: https://stackoverflow.com/a/19263845 So essentially, in .gitattributes: *.cmd eol=crlf On 06/02/2015 03:52 AM, Florent Daigniere wrote: > On Mon, 2015-06-01 at 15:41 -0400, Luke wrote: >> Fairly easily: >> https://unix.stackexchange.com/questions/79702/how-to-test-whether-the-file-is-crlf-or-lf-without-modyfing-it >> >> http://www.microhowto.info/howto/convert_the_line_endings_in_a_text_file_from_unix_to_dos_format.html >> >> FYI, I can confirm that the file is missing CRLF line endings per the >> RAW git from that file. >> >> On 06/01/2015 02:09 PM, Matthew Toseland wrote: >> >>> And can we make the deployment script check for this sort of problem? >>> > > Wrong layer. it's the job of the SCM. > > Decent SCMs allow you to do that ... > http://svnbook.red-bean.com/en/1.7/svn.advanced.props.file-portability.html > > What's the magic git incantation? > > Florent > > > > _______________________________________________ > Devl mailing list > Devl@freenetproject.org > https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
