Skip to content
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

Closed
ghostbar opened this issue Dec 6, 2014 · 9 comments · May be fixed by solebox/node#25, UbuntuEvangelist/node#17, saeedahassan/node#35, erdun/node#41 or enterstudio/node#24

Comments

@ghostbar
Copy link
Contributor

ghostbar commented Dec 6, 2014

It would do everything a lot easier.

@brendanashworth
Copy link
Contributor

👍, this always really annoyed me in the old repository. Can we please also not have a billion branches in this one too?

@mikeal
Copy link
Contributor

mikeal commented Dec 6, 2014

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.

@migounette
Copy link

+1 on board with you @mikeal @indutny @trevnorris @isaacs @bnoordhuis @piscisaureus

@ralphtheninja
Copy link
Contributor

@jbergstroem
Copy link
Member

It seems to be the default branch on github now at least.

@bnoordhuis
Copy link
Member

So it is. I'll go ahead and close the issue.

@bajtos
Copy link
Contributor

bajtos commented Dec 15, 2014

Not for me, https://github.com/iojs/io.js still shows v0.12

@bnoordhuis
Copy link
Member

@bajtos That's the intended behavior. If you do a fresh clone, v0.12 is the default branch.

@bajtos
Copy link
Contributor

bajtos commented Dec 15, 2014

I see. I thought the plan was to rename v0.12 to master. Never mind.

Trott added a commit to Trott/io.js that referenced this issue Apr 25, 2021
The `{colors: true}` removed here is ignored by the function it is being
sent to.
Trott added a commit to Trott/io.js that referenced this issue Apr 25, 2021
The `{colors: true}` removed here is ignored by the function it is being
sent to.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment