RE: Next call on 1/19 or 1/26? Please response asap
Xhafer,
We need to discuss this. Myself I have no issue but what about the others. Any other view? Just speak up.
- Jouni
> -----Original Message-----
> From: Xhafer Krasniqi [mailto:Xhafer.Krasniqi@xxxxxxxxxxxx]
> Sent: Wednesday, January 13, 2016 3:50 AM
> To: Jouni Korhonen; stds-1904-3-tf@xxxxxxxx
> Subject: RE: Next call on 1/19 or 1/26? Please response asap
>
> Hi Jouni,
>
> Following this call on 26th of January, I hope we will continue with the bi-
> weekly schedule on 9th of Feb, 23rd and so on to avoid a clash with another
> call I have on 2nd of Feb, 16th and so on.
>
> Regards
>
> Xhafer
>
> -----Original Message-----
> From: stds-1904-3-tf@xxxxxxxx [mailto:stds-1904-3-tf@xxxxxxxx] On Behalf
> Of Jouni Korhonen
> Sent: 13 January 2016 04:18
> To: stds-1904-3-tf@xxxxxxxx
> Subject: RE: Next call on 1/19 or 1/26? Please response asap
>
> Folks,
>
> The next call will be 1/26/16, since quite a few us are attending to 802 interim
> and I got more preference for 26th. I'll update the invitation shortly.
>
> - Jouni
>
>
>
> > -----Original Message-----
> > From: stds-1904-3-tf@xxxxxxxx [mailto:stds-1904-3-tf@xxxxxxxx] On
> > Behalf Of Jouni Korhonen
> > Sent: Tuesday, January 05, 2016 11:25 AM
> > To: stds-1904-3-tf@xxxxxxxx
> > Subject: Next call on 1/19 or 1/26? Please response asap
> >
> > Folks,
> >
> > Our next normal schedule bi-weekly call is on 1/19, which overlaps
> > with IEEE
> > 802 interim (which e.g. I'll be attending). While 1/19 is doable it
> > might be more convenient to have the call on 1/26 instead. Please
> > indicate me if you favor 1/26 over 1/19 by the end of this week. I'll
> > make a decision based on the received opinions. The default is 1/19
> > unless there are enough voices for 1/26.
> >
> > Thanks,
> > Jouni
> >
> > --
> > Jouni Korhonen, CTO Office, Networking, Broadcom Corporation
> > O: +1-408-922-8135, M: +1-408-391-7160
>
>
> Click
> https://www.mailcontrol.com/sr/99KEfGL0gUHGX2PQPOmvUu5zZAYN1Mos
> a5DwrrVwEBmhPJCmocYMg8y03xVK!2Yg2ds3wsO5tuVjDxGYc2QXWA== to
> report this email as spam.