-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Shouldn't branch v0.12 be master here? #96
Shouldn't branch v0.12 be master here? #96
Comments
👍, this always really annoyed me in the old repository. Can we please also not have a billion branches in this one too? |
this is probably a good idea since our next target version is 1.0 and having a v0.12 branch that differs from Joyent's branch for the target v0.12 release is confusing. |
+1 on board with you @mikeal @indutny @trevnorris @isaacs @bnoordhuis @piscisaureus |
It seems to be the default branch on github now at least. |
So it is. I'll go ahead and close the issue. |
Not for me, https://github.com/iojs/io.js still shows |
@bajtos That's the intended behavior. If you do a fresh clone, v0.12 is the default branch. |
I see. I thought the plan was to rename |
The `{colors: true}` removed here is ignored by the function it is being sent to.
The `{colors: true}` removed here is ignored by the function it is being sent to.
It would do everything a lot easier.
The text was updated successfully, but these errors were encountered: