-
Notifications
You must be signed in to change notification settings - Fork 27
R pkg devel ta #503
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
R pkg devel ta #503
Conversation
This is just a starting point; we can add additional bibEntry values as other sources become available (the glmnet package has a good example of this)
sgsmob
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future would prefer to separate these out into 2-3 separate PRs but what we have here is all ok.
krivard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
I understand the desire to localize changes; that is why I put each resolution into a different commit. However, I don't think there is a way to do a pull request on a specific commit; it is only possible to specify a branch to merge with as far as I am aware. So, I would mean that—unless I stop working each time I resolve an issue while it is reviewed—I need to create brand new branches for every single issue. Is that really necessary? |
Fixing the wrong URL, re: PR #503
Fixing the wrong URL, re: PR #503
This includes several commits which do the follow:
fips_to_nameby splitting into two function, as discussed in Make fips_to_abbr behave in a more predictable way #421