From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: any value in keeping the backward compat "task-core" stuff?
Date: Thu, 10 Jul 2014 11:21:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407101115390.10701@localhost> (raw)
a number of the current packagegroup recipe files still have
backward compatibility support for the old "task-core" names, seems
like that's been there for well over a year, would it be safe to
finally just toss that? seems like everyone's had enough time to make
the move to the new names, and it would be clearer to not confuse the
proper use of the word "task" these days.
thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-07-10 16:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 15:21 Robert P. J. Day [this message]
2014-07-11 23:39 ` [oe] any value in keeping the backward compat "task-core" stuff? Otavio Salvador
2014-07-11 23:39 ` Otavio Salvador
2014-07-14 9:37 ` [oe] " Paul Eggleton
2014-07-14 9:37 ` [OE-core] " Paul Eggleton
2014-07-14 10:13 ` [oe] " Robert P. J. Day
2014-07-14 10:13 ` [OE-core] " Robert P. J. Day
2014-07-14 10:31 ` [oe] " Robert P. J. Day
2014-07-14 10:31 ` [OE-core] " Robert P. J. Day
2014-07-14 11:05 ` [oe] " Paul Eggleton
2014-07-14 11:05 ` [OE-core] " Paul Eggleton
2014-07-14 11:39 ` [oe] " Robert P. J. Day
2014-07-14 11:39 ` [OE-core] " Robert P. J. Day
2014-07-14 12:14 ` [oe] " Paul Eggleton
2014-07-14 12:14 ` [OE-core] " Paul Eggleton
2014-07-14 12:22 ` [oe] " Robert P. J. Day
2014-07-14 12:22 ` [OE-core] " Robert P. J. Day
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=alpine.LFD.2.11.1407101115390.10701@localhost \
--to=rpjday@crashcourse.ca \
--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 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.