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
which repository should be in Metadata? #11
Comments
Agreed, I thought it was like that already outside of the commit access. |
Yes, let's give @jverzani access. I'll look into doing that now. |
I didn't have high enough privileges to give @jverzani access. |
What needs to happen here? |
I thought the decision was to keep this under JuliaLang. If that is the
If someone wants to give my push access that would be helpful going On Mon, Feb 10, 2014 at 11:27 AM, Stefan Karpinski <notifications@github.com
John Verzani |
Sorry about that – I could have sworn I'd already added you. You've got push access now. |
Hope I'm not missing something obvious, but I don't seem to be able to merge #12, which I was hoping to do before updating METADATA with the correct url. |
Bump. Would be nice to have the official version of this package settled. |
Bump. |
Hopefully fixed with 9416279 (manual edits seems to be correct) |
Currently metadata points to jverzani/Roots.jl
We should resolve which repository is the official one. I suggest we use this one, and give @jverzani commit access?
@StefanKarpinski see also discussion here: 7246e1ac37635041bf49bbe75651be5d0e9d5a65
The text was updated successfully, but these errors were encountered: