gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] Copy of IEC 61162-1


From: Chris Kuethe
Subject: Re: [gpsd-dev] Copy of IEC 61162-1
Date: Tue, 7 Apr 2015 11:47:59 -0700

Also, we think that encumbering specifications is pretty stupid,
making people re-implement encumbered standards is pretty stupid...
This approach creates unencumbered reference implementation and
documentation.

On Tue, Apr 7, 2015 at 11:44 AM, Chris Kuethe <address@hidden> wrote:
> Yep, we're lawyer averse because we want gpsd to be usable by anyone
> for any purpose, and we don't have particularly deep war chests.
>
> On Tue, Apr 7, 2015 at 11:01 AM, Sanjeev Gupta <address@hidden> wrote:
>>
>> On Wed, Apr 8, 2015 at 1:25 AM, Eric S. Raymond <address@hidden> wrote:
>>>
>>> Sanjeev Gupta <address@hidden>:
>>> > Would it be useful to the project if I ordered (via the organisation) a
>>> > copy of the latest edition?  Although I cannot share it, I can consult
>>> > the
>>> > hard copy and answer any queries that folks may have.
>>>
>>> *I'd* find it useful.  For one thing, you could check my beliefs abot
>>> NMEA pseudo-PRNs.
>>
>>
>> I'll wait a day, in case someone has a particular reason this may impact the
>> clean-room implementation.
>>
>> (Eric, I understand your aversion to non-distributable documentation, but
>> the docs for GPSD seem positively NMEA-lawyer-averse)
>>
>> --
>> Sanjeev Gupta
>> +65 98551208     http://www.linkedin.com/in/ghane
>
>
>
> --
> GDB has a 'break' feature; why doesn't it have 'fix' too?



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]