From: "Mark Brown" <broonie@gmail.com>
To: kernelci@groups.io, matthew.hart@linaro.org
Subject: Re: New meeting time
Date: Mon, 1 Apr 2019 10:42:44 +0700 [thread overview]
Message-ID: <CACNq6_Y_Nioa3Nb9aDg6SWu1F-6eO+azoXoheLed4RtuP9JF0Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+k93GcepO9OX+6Lof0UEbOPYksymphO_ZKB8bJVuD1QoQDfg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Mon, 25 Mar 2019 at 18:28, Matt Hart <matthew.hart@linaro.org> wrote:
> On Mon, 25 Mar 2019 at 11:23, Mark Brown <broonie@kernel.org> wrote:
> >
> > Hi,
> >
> > It's been just over a week since I sent out the doodle[1] for the new
> > meeting time and we've got responses in. The top options we have allow
> > everyone to attend (at least acording to the survey!):
> >
> > 10 - Monday 14:00
> > - Tuesday 16:00
> > - Friday 15:00 (I will have a conflict every other week)
> > 9 - Monday 15:00 (but no Guillaume)
> >
> > with a bunch of other options with 8 votes. I don't know what my
> > schedule is going to be like in a month or so but I'm guessing the other
> > slots should be fine for me. Given that practically speaking it's
> > difficult for Kevin to attend the Monday 14:00 slot I propose that we go
> > with the Tuesday 16:00 slot since that's the latest one and therefore
> > most friendly to those on PST. Thoughts?
>
> Makes sense to me, as long as it definitely works for our PST folks
It’s a bit late to move this week’s meeting but I’ll move next week’s given
the universal acclaim. Everyone from Linaro is at Connect this week so
attendance is likely to be light.
>
> >
> > Thanks,
> > Mark
> >
> > [1] https://doodle.com/poll/3yb3mzgxt7nqwg87
> >
> >
> >
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2095 bytes --]
prev parent reply other threads:[~2019-04-01 3:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 11:22 New meeting time Mark Brown
2019-03-25 11:27 ` Matt Hart
2019-03-26 0:35 ` Dan Rue
2019-03-26 12:42 ` Mark Brown
2019-03-29 17:20 ` Kevin Hilman
2019-04-01 3:42 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACNq6_Y_Nioa3Nb9aDg6SWu1F-6eO+azoXoheLed4RtuP9JF0Q@mail.gmail.com \
--to=broonie@gmail.com \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.