From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: proposal: remove DirectFB from oe-core in the next release cycle
Date: Fri, 22 Jan 2016 16:38:16 +0100 [thread overview]
Message-ID: <56A24CE8.8010501@opendreambox.org> (raw)
In-Reply-To: <56A22767.7050000@linux.intel.com>
On 22.01.2016 13:58, Alexander Kanavin wrote:
> Hello,
>
> DirectFB upstream project has been dead for several months, the website
> has completely disappeared, and no explanation or apology has ever
> surfaced. [1]
>
> So let's keep DirectFB in the forthcoming release, but drop it early in
> the next release cycle.
>
> [1] http://www.phoronix.com/scan.php?page=news_item&px=DirectFB-Is-It-Gone
FWIW, https://github.com/deniskropp/DirectFB is the new location of the
upstream repository. I see that you opened an issue there, so you're
already aware. The last commit is from October 2015.
I guess many other projects in OE-Corew have seen much less activity. So
what's the real reason for this proposal? Failing update scripts?
Regards,
Andreas
next prev parent reply other threads:[~2016-01-22 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 12:58 proposal: remove DirectFB from oe-core in the next release cycle Alexander Kanavin
2016-01-22 13:04 ` Otavio Salvador
2016-01-22 15:38 ` Andreas Oberritter [this message]
2016-01-22 16:12 ` Burton, Ross
2016-01-22 18:06 ` Andreas Oberritter
2016-01-22 18:12 ` Burton, Ross
2016-01-22 19:10 ` alexander.kanavin
2016-01-22 18:49 ` Khem Raj
2016-02-01 10:21 ` Burton, Ross
2016-02-01 19:13 ` Andre McCurdy
2016-02-01 20:54 ` Burton, Ross
2016-01-22 18:47 ` Khem Raj
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=56A24CE8.8010501@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@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.