Am 02.09.2016 um 16:02 schrieb Dirk Eddelbuettel:
On 2 September 2016 at 14:54, Thomas Petzoldt wrote:
| Hi,
|
| I have the same problem and, at a first look, the issues reported by the
| CRAN checks seemed easy to fix. However, after checking it again locally
| and on
On 2 September 2016 at 14:54, Thomas Petzoldt wrote:
| Hi,
|
| I have the same problem and, at a first look, the issues reported by the
| CRAN checks seemed easy to fix. However, after checking it again locally
| and on http://win-builder.r-project.org it appeared that GCC 4.9.3
| (Windows,
Hi,
I have the same problem and, at a first look, the issues reported by the
CRAN checks seemed easy to fix. However, after checking it again locally
and on http://win-builder.r-project.org it appeared that GCC 4.9.3
(Windows, Rtools 3.4), same also on win-builder reports even more
issues,
Hi Kurt,
I have started to look into this, and I need some guidance about how to
prioritize my repairs. There are basically 4 categories of warnings from
gfortran’s pedantic critique of my packages:
1. Some errant tab characters it doesn’t like,
2. Too many or too few continue
It is A Good Thing to regularize Authors and Maintainers of packages,
particularly for citation()
and toBibTex().
Could I add a suggested TODO item for the maintainer of package.skeleton
and friends to
help reinforce this for new packages:
- Please add appropriate templates for Author@R in
On Sat, 2007-04-07 at 08:40 +0200, Kurt Hornik wrote:
Dear maintainers of CRAN packages,
This concerns the packages
snip /
And now keep the updates rolling in ...
Dear R Developers,
I was recently emailed by the CRAN maintainers about warnings for my two
packages, analog and cocorresp,
