From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, dan.rue@linaro.org, kernelci@groups.io
Subject: Re: Weekly Meeting 2018-12-17 #minutes
Date: Mon, 17 Dec 2018 12:27:18 -0800 [thread overview]
Message-ID: <7hpntzlx09.fsf@baylibre.com> (raw)
In-Reply-To: <20181217154926.6qyfw2a6y5oidkny@xps.therub.org>
"Dan Rue" <dan.rue@linaro.org> writes:
> - Attendees: Charles Oliveira, Daniel Díaz, Guenter Roeck, Guillaume
> Tucker, Milosz Wasilewski, Dan Rue, Mark Brown
>
> - [drue] I received this when replying to -stable RCs on Saturday: “Your
> message wasn't delivered to patches@kernelci.org because the address
> couldn't be found, or is unable to receive mail.”
> - Tyler deleted it as it’s not used for anything and he’s still paying
> out of pocket for hosting the domain
> - Greg will need to remove this from the list of recipients for
> stable-rc
Hmm, this might break the backend code which is replying to the
stable-rc mails.
We may have deleted that alias too soon (my fault, I told Tyler I didn't
hink it was being used.)
Kevin
prev parent reply other threads:[~2018-12-17 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 15:49 Weekly Meeting 2018-12-17 #minutes Dan Rue
2018-12-17 20:27 ` Kevin Hilman [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=7hpntzlx09.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=dan.rue@linaro.org \
--cc=kernelci@groups.io \
/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