From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
Jason Kridner <jdk@ti.com>, "Wold, Saul" <saul.wold@intel.com>
Subject: Re: Documenting the mailing lists.
Date: Tue, 21 Aug 2012 00:19:16 +0100 [thread overview]
Message-ID: <336378798.CjWX3CWzPu@helios> (raw)
In-Reply-To: <5032BF3D.4000900@linux.intel.com>
On Monday 20 August 2012 15:50:37 Darren Hart wrote:
> On 08/20/2012 03:43 PM, Jeff Osier-Mixon wrote:
> > On Mon, Aug 20, 2012 at 3:37 PM, Darren Hart <dvhart@linux.intel.com>
wrote:
> >> On 08/20/2012 03:18 PM, Jeff Osier-Mixon wrote:
> >>> The mailing lists and website stuff is generally my responsibility,
> >>> but please fix anything you like. :) Be aware that the new website is
> >>
> >> No intent to take over anything, I've just had to answer the "what goes
> >> where" question a few too many times these last couple of weeks and felt
> >> I should do something about it :-)
> >
> > Oh, I'm not joking - please fix anything you want! or Scott or I can
> > do it. Thanks for getting the ball rolling. I'll catch up on this
> > thread.
> >
> >> I made sure you were on CC so you could help guide this.
> >>
> >>> under construction, so I am loathe to change much on the old website
> >>> at this point. For the new one, it may be possible to dynamically
> >>> grab the description from mailman.
> >>
> >> We'll still need descriptions of the non-yocto-project lists, so that
> >> may not be particularly helpful.
> >
> > The only YP-related, non-YP lists I currently track are
> > openembedded-core and bitbake-devel. Both are OE lists, and I have
> > recently volunteered to help admin, so can make sure they have valid
> > Descriptions. If there are other lists we should track, please let me
> > know and I'll add them to the pile.
>
> The only additional one that we reference in the manual is:
>
> * http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> - Discussion mailing list about OpenEmbedded.
>
> I'm not sure we need reference it at all though, perhaps oe-core is
> sufficient.
FYI, the reason I added oe-devel is because it's the list that is used to
discuss/submit patches for almost all OE community layers other than OE-Core
and the ones that are hosted on yoctoproject.org.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-20 23:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 18:43 Documenting the mailing lists Darren Hart
2012-08-20 19:15 ` Denys Dmytriyenko
2012-08-20 20:55 ` Rifenbark, Scott M
2012-08-20 21:19 ` Darren Hart
2012-08-20 21:23 ` Rifenbark, Scott M
2012-08-20 21:19 ` Denys Dmytriyenko
2012-08-20 21:26 ` Paul Eggleton
2012-08-20 21:27 ` Darren Hart
2012-08-20 21:33 ` Paul Eggleton
2012-08-20 21:34 ` Rifenbark, Scott M
2012-08-20 21:53 ` Hudson, Sean
2012-08-20 22:04 ` Darren Hart
2012-08-20 22:22 ` Rifenbark, Scott M
2012-08-20 21:40 ` Hudson, Sean
2012-08-20 21:56 ` Michael Halstead
2012-08-20 22:06 ` Darren Hart
2012-08-20 22:18 ` Jeff Osier-Mixon
2012-08-20 22:37 ` Darren Hart
2012-08-20 22:43 ` Jeff Osier-Mixon
2012-08-20 22:50 ` Darren Hart
2012-08-20 23:19 ` Paul Eggleton [this message]
2012-08-21 16:28 ` Darren Hart
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=336378798.CjWX3CWzPu@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=jdk@ti.com \
--cc=saul.wold@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.