[
https://issues.apache.org/jira/browse/ZOOKEEPER-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062032#comment-14062032
]
Bill Havanki commented on ZOOKEEPER-1953:
-----------------------------------------
Thanks for the links, [~oho]. From looking at those and others, and messing
around some, I was able to eliminate the warnings by temporarily adding to
.gitattributes:
{noformat}
*.vcxproj -text
*.vcxproj.filters -text
zookeeper-vs2013.sln -text
{noformat}
Oddly, even after removing those changes, the warnings stay gone.
(I can get the warnings back by deleting the five files and doing a {{git reset
--hard HEAD}}. Temporarily modifying .gitattributes fixes it again. So weird.)
I think the best course of action is to update the new files to be "normalized"
in Git (i.e., in the Git repository) to have LF endings, and to add
.gitattributes entries for them akin to what's there for other files that
require CRLF:
{noformat}
*.vcxproj text merge=union eol=crlf
*.vcxproj.filters text merge=union eol=crlf
{noformat}
> Add solution and project files to enable build with current Visual Studio
> editions (VS 2012/2013) - 32-bit and 64-bit.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1953
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1953
> Project: ZooKeeper
> Issue Type: Improvement
> Components: c client
> Affects Versions: 3.5.0
> Reporter: Patrick Hunt
> Assignee: Orion Hodson
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1953-1.patch, ZOOKEEPER-1953.patch
>
>
> Add solution and project files to enable build with current Visual Studio
> editions (VS 2012/2013) - 32-bit and 64-bit.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
