All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Bunk" <bunk@stusta.de>
To: Stephen Jolley <sjolley.yp.pm@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto Project Status WW04'20
Date: Sun, 2 Feb 2020 15:28:40 +0200	[thread overview]
Message-ID: <20200202132840.GA6805@localhost> (raw)
In-Reply-To: <086201d5d5f4$307b2150$917163f0$@gmail.com>

On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
>...
> *	We have created a "documentation" list and a "licensing" list on the
> yocto project mailing list infrastructure. We believe these topics would
> benefit from dedicated discussions, the people involved usually aren't
> interested in bulk email as would be found on other lists. The new lists can
> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
> https://lists.yoctoproject.org/g/licensing/join and
> <https://lists.yoctoproject.org/g/docs/join>
> https://lists.yoctoproject.org/g/docs/join 
>...

Would it be possible to also create a yocto-devel or yocto-core
mailing list for discussing development of Yocto?

Currently the yocto list is a mixture of core development list and forum 
for newbie user questions, with no easy way to have them separate.

Thanks
Adrian

  reply	other threads:[~2020-02-02 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 16:01 Yocto Project Status WW04'20 sjolley.yp.pm
2020-01-28 16:01 ` Stephen Jolley
2020-02-02 13:28 ` Adrian Bunk [this message]
2020-02-02 14:09   ` [yocto] " Alexander Kanavin
2020-02-02 18:48     ` Chuck Wolber
2020-02-02 19:36     ` Josef Holzmayr
2020-02-02 15:16   ` Ross Burton
2020-02-02 18:10     ` Adrian Bunk
2020-02-02 18:18   ` Philip Balister
2020-02-03 16:16     ` akuster
2020-02-03 21:05       ` Denys Dmytriyenko
2021-03-16 14:05     ` DUDZIAK Krzysztof

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=20200202132840.GA6805@localhost \
    --to=bunk@stusta.de \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yocto@yoctoproject.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.