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

Support atom-shell 0.21 #276

Merged
merged 2 commits into from
Feb 8, 2015
Merged

Support atom-shell 0.21 #276

merged 2 commits into from
Feb 8, 2015

Conversation

kkoopa
Copy link
Collaborator

@kkoopa kkoopa commented Feb 7, 2015

This should get atom-shell working again.
Addresses #226.

@bnoordhuis
Copy link
Member

LGTM but perhaps consider breaking out the number literals into defines.

@kkoopa
Copy link
Collaborator Author

kkoopa commented Feb 8, 2015

Aye

@bnoordhuis
Copy link
Member

LGTM

kkoopa added a commit that referenced this pull request Feb 8, 2015
Support atom-shell 0.21
@kkoopa kkoopa merged commit 1c811c9 into master Feb 8, 2015
@kkoopa kkoopa deleted the atom branch February 8, 2015 14:29
@zcbenz
Copy link

zcbenz commented Feb 12, 2015

💖

@maxkorp
Copy link
Contributor

maxkorp commented Feb 12, 2015

Awesome!!!
What's the timeline for this making it into a release? I've tested building nodegit for atom shell 0.21 against nan@master and it works, but we'd like to avoid versioning against a specific sha. We're not planning on releasing for another week or two at least probably, so its not super urgent, but I know 2.0 is slated as vNext and I imagine that taking a while potentially. If it's not gonna take a long time then nevermind, but if it's gonna be a month or two, any chance of a dot release?

@johnhaley81
Copy link

👍 :)

@kkoopa
Copy link
Collaborator Author

kkoopa commented Feb 12, 2015

No worries. I'll still put out master as 1.7.0 within a week or two. After that, things should hopefully stabilize for a while so we can work on 2.0.

On February 12, 2015 8:26:22 PM EET, Max Korp [email protected] wrote:

Awesome! What's the timeline for this making it into a release?
I've tested building nodegit for atom
shell 0.21 against nan@master and it works, but we'd like to avoid
versioning against a specific sha. We're not planning on releasing for
another week or two at least probably, so its not super urgent, but I
know 2.0 is slated as vNext and I imagine that taking a while
potentially. If it's not gonna take a long time then nevermind, but if
it's gonna be a month or two, any chance of a dot release?


Reply to this email directly or view it on GitHub:
#276 (comment)

@maxkorp
Copy link
Contributor

maxkorp commented Feb 12, 2015

Sweet, thanks!

@johnhaley81
Copy link

Hey @kkoopa, just a friendly ping on the status of 1.7.0 :)

@kkoopa
Copy link
Collaborator Author

kkoopa commented Feb 18, 2015

I guess #284 that just came in is the only blocker now that #278 has been sorted out. ETA is around 1 week, in time for March.

@johnhaley81
Copy link

Sounds great! Thanks for the update.

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.

5 participants