Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Use mono 3.6 #800

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

Merged
merged 1 commit into from
Aug 31, 2014
Merged

Use mono 3.6 #800

merged 1 commit into from
Aug 31, 2014

Conversation

carlosmn
Copy link
Member

No description provided.

@carlosmn carlosmn force-pushed the cmn/mono-3 branch 5 times, most recently from 8483865 to 7c51a15 Compare August 26, 2014 15:18
@nulltoken
Copy link
Member

/cc @Therzok

@Therzok
Copy link
Member

Therzok commented Aug 26, 2014

LGTM, both travis lanes are picking up 3.6.0 Mono. This also means that the copy target works for Unix too.

@nulltoken
Copy link
Member

This also means that the copy target works for Unix too.

@Therzok Yep. #733 shouldn't be an issue any longer if we go forward with this 😉

How do you feel about not supporting mono 2.10.8 any longer?

/cc @dragan

@Therzok
Copy link
Member

Therzok commented Aug 26, 2014

@nulltoken scrap that, the copy target for Unix is broken. We actually copy windows native git files. Shouldn't we just make that target Windows-only? :P

Also, to get this up and known. Linux world is getting more love on mono packages.

@nulltoken
Copy link
Member

Shouldn't we just make that target Windows-only? :P

@Therzok I agree. Do you feel like sending a PR?

Also, to get this up and known. Linux world is getting more love on mono packages.

Does this mean that moving to 3.6 wouldn't hurt the Mono community too much?

@Therzok
Copy link
Member

Therzok commented Aug 26, 2014

@nulltoken considering the green light on dropping the target for linux, we're not hurting them at all.

It was only erroring on running, not parsing.

@Therzok
Copy link
Member

Therzok commented Aug 30, 2014

This can go in imo.

@nulltoken nulltoken merged commit 290e4ff into vNext Aug 31, 2014
@nulltoken nulltoken deleted the cmn/mono-3 branch August 31, 2014 13:58
@nulltoken
Copy link
Member

This can go in imo.

Right. It's in now.

@carlosmn Thanks for this. 😍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants