[
https://issues.apache.org/jira/browse/SOLR-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635615#comment-13635615
]
Uwe Schindler commented on SOLR-4731:
-------------------------------------
Yeah, that's exactly the problem.
The Lucene team can do nothing about that. Lucene uses Subversion for its
source code management. The GIT repository is provided for convenience to
external developers by GITHUB and the ASF infra team. The bug here is that GIT
does not know svn:eol-style properties.
> Fresh clone of github lucene-solr repo already has modified files somehow
> -------------------------------------------------------------------------
>
> Key: SOLR-4731
> URL: https://issues.apache.org/jira/browse/SOLR-4731
> Project: Solr
> Issue Type: Bug
> Reporter: Uri Laserson
> Attachments: weird.diff
>
>
> I forked the lucene-solr repo on github.
> Then
> git clone [email protected]:laserson/lucene-solr.git
> Then `git status` gives me
> $ git status
> # On branch trunk
> # Changes not staged for commit:
> # (use "git add <file>..." to update what will be committed)
> # (use "git checkout -- <file>..." to discard changes in working directory)
> #
> # modified: solr/example/cloud-scripts/zkcli.bat
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> Even though I never touched anything
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
