On 13-08-18 10:04, Vincent Dupont wrote:
Hi Kees,
Le dimanche 12 août 2018 à 14:44 +0200, Kees Bakker a écrit :
On 10-08-18 09:10, Kaspar Schleiser wrote:
He Kees,
On 08/05/2018 01:20 PM, Kees Bakker wrote:
First of all, who is the maintainer of driver_at? In other words,
who should I be ask
Hi Kees,
Le dimanche 12 août 2018 à 14:44 +0200, Kees Bakker a écrit :
> On 10-08-18 09:10, Kaspar Schleiser wrote:
> > He Kees,
> >
> > On 08/05/2018 01:20 PM, Kees Bakker wrote:
> > > First of all, who is the maintainer of driver_at? In other words,
> > > who should I be asking questions about
On 10-08-18 09:10, Kaspar Schleiser wrote:
He Kees,
On 08/05/2018 01:20 PM, Kees Bakker wrote:
First of all, who is the maintainer of driver_at? In other words,
who should I be asking questions about this driver?
As I'm the original author, I'd consider myself the author, but Vincent
has contr
He Kees,
On 08/05/2018 01:20 PM, Kees Bakker wrote:
> First of all, who is the maintainer of driver_at? In other words,
> who should I be asking questions about this driver?
As I'm the original author, I'd consider myself the author, but Vincent
has contributed a lot. Asking on this mailing list
Hi,
There wasn't any reaction to my question, so I'm trying again.
Or, should I be opening an issue at GitHub?
Besides my question about the handling of URCs, I'm quite curious
if there are people using the generic AT module.
-- Kees
On 05-08-18 13:20, Kees Bakker wrote:
Hey,
First of all, wh
