t;> Any hopes out there?
>>
>> Thx
>>
>> ~Malcolm
>>
>>
>>> -----Original Message-----
>>> From: Kasper Daniel Hansen [mailto:kasperdanielhan...@gmail.com]
>>> Sent: Tuesday, November 06, 2012 2:32 PM
>>> To: Cook, Mal
>>
>>
>>> -----Original Message-----
>>> From: Kasper Daniel Hansen [mailto:kasperdanielhan...@gmail.com]
>>> Sent: Tuesday, November 06, 2012 2:32 PM
>>> To: Cook, Malcolm
>>> Cc: Bioconductor Newsgroup (bioconduc...@stat.math.ethz.ch);
>>&
/bioconductor.org/rss/new_packages.rss
Hope this helps,
Laurent
> Any hopes out there?
>
> Thx
>
> ~Malcolm
>
>
>> -Original Message-
>> From: Kasper Daniel Hansen [mailto:kasperdanielhan...@gmail.com]
>> Sent: Tuesday, November 06, 2012 2:32 PM
>>
onductor Newsgroup (bioconduc...@stat.math.ethz.ch);
> bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] knowing what is changed/new in release patches
>
> A package may choose to provide a NEWS file which you should be able
> to access using
>news(package = "IRanges"
A package may choose to provide a NEWS file which you should be able
to access using
news(package = "IRanges")
(you can also ask for news added after a given version number, the
query above lists the entire file). It is optional to include and it
is optional how detailed it is, but this is inte
Is there a generic way to learn what is changed or new in a "released" package
since its release?
For instance, IRanges was released as 1.16.0 but is now at 1.16.4.
I'd like to know what was changed in this released version.
I do already know that I can monitor changes to devel with either
