We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Maybe build on r-spatial/discuss#39, aiming to reduce issue pressure from source installers, see also https://stat.ethz.ch/pipermail/r-sig-geo/2020-May/028125.html, https://stat.ethz.ch/pipermail/r-sig-geo/2020-May/028131.html, and a brilliant reply from Simon Urbanek, who is not on R-sig-geo, so the reply only went to direct addressees - I can ask him if we can use parts of it. Need to explain the logic and consequences of CRAN binaries. Cant take up metadata duplication matters.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Maybe build on r-spatial/discuss#39, aiming to reduce issue pressure from source installers, see also https://stat.ethz.ch/pipermail/r-sig-geo/2020-May/028125.html, https://stat.ethz.ch/pipermail/r-sig-geo/2020-May/028131.html, and a brilliant reply from Simon Urbanek, who is not on R-sig-geo, so the reply only went to direct addressees - I can ask him if we can use parts of it. Need to explain the logic and consequences of CRAN binaries. Cant take up metadata duplication matters.
The text was updated successfully, but these errors were encountered: