-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CCd to r-devel as suggested by Peter.
On 09/02/12 19:28, Hadley Wickham wrote:
>>> I'm exploring using a version control system to keep better
>>> track of changes to the packages I maintain. I'm leaning
>>> towards git (although mercurial also looks
Could I gently remind you guys about the R-help litmus test: If an ordinary R
_user_ has no clue what you are on about, you are on the wrong list. R-devel
would be right.
-pd
On Feb 9, 2012, at 19:28 , Hadley Wickham wrote:
>>> I'm exploring using a version control system to keep better track
>> I'm exploring using a version control system to keep better track
>> of changes to the packages I maintain. I'm leaning towards git
>> (although mercurial also looks good) but am not sure what is the
>> best way to set up the repository. It seems I can't set the
>> repository directly within the
> Same warning here. Which made me think that R CMD build will probably
> tar up the git repository along with the package, which is not
> something I would like to do, and which CRAN people most likely won't
> tolerate in a package on CRAN.
It doesn't. And you can always use .Rbuildignore to ign
On Thu, Feb 9, 2012 at 1:46 AM, Gregory Jefferis wrote:
> Dear Peter,
>
> Trying to respond to your original question
Thanks for staying on thread :)
>
>
> I have a git repositiory in the root of my packages:
>
> ie
>
> package-foo/.git
> package-foo/R
> package-foo/inst
>
> Running make check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/02/12 10:09, baptiste auguie wrote:
> Once upon a time r-forge had the option to sync from an external
> svn repository, e.g. hosted on googlecode. I haven't seen it
> available for some time, sadly. I'm sure many users would
> appreciate if t
Once upon a time r-forge had the option to sync from an external svn
repository, e.g. hosted on googlecode. I haven't seen it available for
some time, sadly. I'm sure many users would appreciate if this feature
came back with the new interface. Not sure if it could work with git
as well, though.
b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/02/12 00:33, Tom Roche wrote:
>
> Peter Langfelder Thu Feb 9 00:01:31 CET 2012
>> I'm exploring using a version control system
>
> +1! welcome to the new millenium :-)
>
>> to keep better track of changes to the [R] packages I maintain.
>> I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/02/12 00:01, Peter Langfelder wrote:
> Hi all, in particular package developers,
>
> I'm exploring using a version control system to keep better track
> of changes to the packages I maintain. I'm leaning towards git
> (although mercurial also lo
On 9 February 2012 13:02, David Winsemius wrote:
>
> On Feb 8, 2012, at 6:33 PM, Tom Roche wrote:
>
>>
>> Peter Langfelder Thu Feb 9 00:01:31 CET 2012
>>>
>>> I'm exploring using a version control system
>>
>>
>> +1! welcome to the new millenium :-)
>>
>>> to keep better track of changes to the [R
On Feb 8, 2012, at 6:33 PM, Tom Roche wrote:
Peter Langfelder Thu Feb 9 00:01:31 CET 2012
I'm exploring using a version control system
+1! welcome to the new millenium :-)
to keep better track of changes to the [R] packages I maintain. I'm
leaning towards git
I like 'git' too, but one t
Peter Langfelder Thu Feb 9 00:01:31 CET 2012
> I'm exploring using a version control system
+1! welcome to the new millenium :-)
> to keep better track of changes to the [R] packages I maintain. I'm
> leaning towards git
I like 'git' too, but one thing to consider (though keep in mind that
I'm
Hi all, in particular package developers,
I'm exploring using a version control system to keep better track of
changes to the packages I maintain. I'm leaning towards git (although
mercurial also looks good) but am not sure what is the best way to set
up the repository. It seems I can't set the re
13 matches
Mail list logo
