public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Mark Brown <broonie@kernel.org>, kernelci@groups.io
Cc: Dan Rue <dan.rue@linaro.org>
Subject: Re: [kernelci] Some suggestions and questions
Date: Fri, 14 Dec 2018 13:51:19 -0800	[thread overview]
Message-ID: <7hwoobn5ew.fsf@baylibre.com> (raw)
In-Reply-To: <20181214180644.GE6467@sirena.org.uk>

Mark Brown <broonie@kernel.org> writes:

> On Fri, Dec 14, 2018 at 10:00:38AM -0800, Kevin Hilman wrote:
>> "Dan Rue" <dan.rue@linaro.org> writes:
>
>> > In the interest of transparency, can we disclose how emails sent to
>> > info@kernelci.org are handled?
>
>> This predates the list, so any new mails (of which there are almost
>> none) are redirected to the mailing list. 
>
>> I think to fix this, we need to fix the /contact page to point to the
>> groups.io list instead of the info alias.
>
> Could we just point the alias at the list perhaps?  It's kind of nice
> that it's an @kernelci.org mail (and we might want to reorganize that
> again when the LF project launches anyway).

Done.

alias now points to the list.

Kevin

      reply	other threads:[~2018-12-14 21:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 21:38 Some suggestions and questions Dan Rue
2018-12-13 11:49 ` [kernelci] " Mark Brown
2018-12-13 12:14   ` Mike Holmes
2018-12-13 12:34     ` Mark Brown
2018-12-13 15:29       ` Dan Rue
2018-12-13 16:19         ` Mark Brown
2018-12-13 16:33           ` Dan Rue
2018-12-13 16:38             ` Mark Brown
     [not found] ` <156FE20DF2374CC6.18828@groups.io>
2018-12-13 12:15   ` [kernelci] " Mark Brown
2018-12-14 18:00 ` Kevin Hilman
2018-12-14 18:06   ` Mark Brown
2018-12-14 21:51     ` 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=7hwoobn5ew.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=broonie@kernel.org \
    --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