Oh, I just put that there for the bit about "WITHOUT ANY WARRANTY" :). I
am satisfied with GPLv2 and have updated the license notice to reflect a
change from GPLv3 to GPLv2 or later.
-Matt
On Tue, 2010-04-27 at 09:33 -0400, Peter Dalgaard wrote:
> On Apr 27, 2010, at 2:42 PM, Duncan Murdoch wrote
On Apr 27, 2010, at 2:42 PM, Duncan Murdoch wrote:
> On 27/04/2010 8:32 AM, Matt Shotwell wrote:
>> Simon,
>> Thanks for reviewing it! All the modified files are under the GPL
>> version 2 (except the configure script). According to the GPLv2, I am
>> granted permission to modify and redistribut
On 27/04/2010 8:32 AM, Matt Shotwell wrote:
Simon,
Thanks for reviewing it! All the modified files are under the GPL
version 2 (except the configure script). According to the GPLv2, I am
granted permission to modify and redistribute the code as long as I make
a notice in the files of their modi
Simon,
Thanks for reviewing it! All the modified files are under the GPL
version 2 (except the configure script). According to the GPLv2, I am
granted permission to modify and redistribute the code as long as I make
a notice in the files of their modification and the date (which I have
not done y
Matt,
thanks for you efforts. We cannot directly use your patch due to licensing
issues (please note the licenses in the files you are modifying - I don't think
anyone can currently use the patch and redistribute the resulting R; also/or we
may possibly need to clarify that the work is either d
All,
Our discussion of serial interfaces last week motivated me to dig into
the R connections API. In short, I spent the weekend writing a patch for
version 2.11.0 that adds a serial connection. I posted a blog entry that
gives instructions for applying, configuring, and compiling the patched
ver
