Hal Murray :
> Or maybe a json designed for ntpd rather than gpsd.
I like that plan. (As long as there's a receipt-timestamp field
so the client can compensate for parse latency.) All the issues that
make JSON a good choice for GPSD bear on this, too, IMO.
--
http://www.catb.org/
On Sun, May 27, 2018 at 11:56 AM Hal Murray via devel
wrote:
>
> Eric said:
> > SINGLESOCK: While messy and somewhat difficult, this is mostly a SMOP
> > (Simple Matter of Programming). There is one potential technical risk,
> > relatively minor I think.
>
> > The reason for iterating over inter
There are a small core of trusted people who currently have ACLs and
blessing to develop with "git push", mainly ESR, GEM, Hal, and DFF, (and
myself when I'm cutting a release).
Everyone else is to use gitlab merge requests, and now MR's with the code
review voting that Matthew has set up.
Hal,
