From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: New development mailing list for the linux-yocto kernel repository
Date: Thu, 19 Jul 2012 15:50:36 -0700 [thread overview]
Message-ID: <50088F3C.5060500@linux.intel.com> (raw)
The linux-yocto git repositories contain both Linux kernel sources as
well as the meta-data used to prepare the BSP specific source branches
and assemble the kernel config file. Much of this development has only
been visible when the SRCREV update request is sent to update the
various recipes.
In an effort to make this process more transparent, we decided all such
changes should hit a mailing list for review. However, we didn't feel it
was appropriate to use any of the existing lists as there is potential
for a large number of small patches, especially for meta-data cleanup
and reorganization, that will be of little interest to most of the
subscribers. As the sources are inherently different from any
recipe-based repositories, we created a new list:
https://lists.yoctoproject.org/listinfo/linux-yocto
"Development list for the linux-yocto git repositories. Patches for the
various KTYPE and BSP branches as well as meta-data should be sent to
this list for review and discussion."
If you are an active contributor to any of the linux-yocto*.git
repositories, please submit your patches there.
Please note that this is NOT for the linux-yocto recipes and classes
that are part of oe-core. Development discussions and patches for those
should remain on the oe-core mailing list as they deal with recipes that
are hosted in that repository.
Thanks,
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
reply other threads:[~2012-07-19 22:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50088F3C.5060500@linux.intel.com \
--to=dvhart@linux.intel.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.