From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: OE-Classic patches in patchwork
Date: Tue, 04 Dec 2012 18:11:22 +0000 [thread overview]
Message-ID: <3145293.jEgb7vZ7zI@helios> (raw)
Hi all,
There is a significant volume of patches in the OE patchwork [1] that are
intended to apply to OE-Classic. Apart from the 2011.3-maintenance branch, OE-
Classic is no longer maintained in favour of OE-Core + layers, so the question
is what should we do with these patches? At the moment I'm thinking we should
just mark them as "archived" so that they disappear from the queue; people can
still get access to them if needed.
Thoughts?
Cheers,
Paul
[1] http://patchwork.openembedded.org/project/oe/list/
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2012-12-04 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 18:11 Paul Eggleton [this message]
2012-12-04 19:39 ` OE-Classic patches in patchwork Otavio Salvador
2012-12-13 23:20 ` Martin Jansa
2012-12-14 11:05 ` Martin Jansa
2013-01-15 23:49 ` Archived patchwork entries Was: " Martin Jansa
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=3145293.jEgb7vZ7zI@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox