public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: kernelci@groups.io
Cc: alan@opensourcefoundries.com, tyler@opensourcefoundries.com
Subject: Re: Moving meeting time
Date: Thu, 26 Jul 2018 17:35:28 +0100	[thread overview]
Message-ID: <20180726163528.GL2414@sirena.org.uk> (raw)
In-Reply-To: <20180726150934.GH2414@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Thu, Jul 26, 2018 at 04:09:34PM +0100, Mark Brown wrote:

> Looking at the results there the most popular options are
> (Europe/London):
> 
>    Monday   1400 (10 votes, everyone except Kevin)

We discussed this during the meeting today and agreed that this is
probably the best option we have, obviously we'll miss Kevin most of the
time but it means it's not in prime commute time for Europe.

Tyler, we think you're the only person with edit rights to the meeting -
can you do the honours?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-07-26 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 15:09 Moving meeting time Mark Brown
2018-07-26 16:35 ` 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=20180726163528.GL2414@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alan@opensourcefoundries.com \
    --cc=kernelci@groups.io \
    --cc=tyler@opensourcefoundries.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox