[
https://issues.apache.org/jira/browse/LUCENENET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149204#comment-13149204
]
Prescott Nasser commented on LUCENENET-453:
-------------------------------------------
Hey Stefan is test/contrib/Core/Analysis/Ext/Analysis.Ext.Test.cs the only file
with the bad mime-type? Also, how do you run a scan on all files for something
like this? I have no idea now that works.
Also for 'build.cmd should likely get an svn:eol-style of crlf' what does that
mean exactly? (Sorry out of my depth here)
> Many files need proper svn properties to set the linefeeds
> ----------------------------------------------------------
>
> Key: LUCENENET-453
> URL: https://issues.apache.org/jira/browse/LUCENENET-453
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Stefan Bodewig
> Priority: Minor
> Attachments: LUCENENET-453.inconsistent-eol.patch,
> LUCENENET-453.list-of-files-with-missing-svn_eol-style.txt
>
>
> Many files are lacking the svn:eol-style proper which should be set to
> native, I'll attach a list later.
> Some files have inconsistent linefeeds, I'll attach a patch.
> Some files even have bad mine-types. You need to run
> svn pd svn:mime-type
> on
> test/contrib/Core/Analysis/Ext/Analysis.Ext.Test.cs
> build.cmd should likely get an svn:eol-style of crlf
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
