-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github files WIP #96
Github files WIP #96
Conversation
sorry about this, but could you please rebase on current master? |
Yeah, will do tonight. Have there been any major changes since the weekend? |
Unfortunatly yes. 2014-09-15 17:30 GMT+02:00 Isaac Abraham [email protected]:
|
Hmmm. I've seen that "cleanup" commit already - it was what broke the previous PR. This PR should actually cater for that, and indeed it wasn't complaining about merge conflicts when I submitted it, so it must be something else that's caused the conflict. |
oh it doesn't have a "git merge conflict", but the merged file is invalid. 2014-09-15 18:05 GMT+02:00 Isaac Abraham [email protected]:
|
Are you sure that's for this PR? The other one was invalid, this one shouldn't be. |
Mhm. The merge doesn't build on my machine.
|
Merge to what - which commit? |
I merged to master and the build failed.
|
but don't worry. Will try again - and make it work. |
I renamed the Resolver.fs file to PackageResolve.fs - that might be the cause of the conflict. |
Maybe we could add merge=text for the *.fs files in the .gitattributes file |
@theimowski nice catch. 2be02dd |
Cool. Did it get all the code I merged in this morning (which actually modifies the project file)? I haven't tested it on an fsproj ever - just that test csproj. |
Mhm Yes I hope I merged everything. Please review the last commits
|
Yes looks like it all got in. From: Steffen Forkmann [mailto:[email protected]] Mhm Yes I hope I merged everything. Please review the last commits
— |
As per previous WIP PR for #9. However, this one actually builds!