From: Philip Balister <philip@balister.org>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: unmaintained layers
Date: Thu, 09 Jan 2014 20:14:43 -0500 [thread overview]
Message-ID: <52CF4983.4070501@balister.org> (raw)
In-Reply-To: <52CF2ED0.8090605@linaro.org>
On 01/09/2014 06:20 PM, Trevor Woerner wrote:
> On 01/09/14 17:43, Mark Hatle wrote:
>> On 1/9/14, 3:45 PM, Bruce Ashfield wrote:
>>> On Thu, Jan 9, 2014 at 1:45 PM, Trevor Woerner
>>> <trevor.woerner@linaro.org> wrote:
>>>> Hi everyone,
>>>>
>>>> At the last TSC meeting the topic of unmaintained layers came up. Here
>>>> is the sorted list of master layers from the layer index [1], would it
>>>> be possible for those in the know to indicate which layers are, or are
>>>> suspected of being, unmaintained?
>>>
>>> Wouldn't it be easier to do an initial sort based on commit activity
>>> ? Versus an
>>> opt-in query ?
>>
>> I agree.. see below for mine..
>
> To be honest, I had asked people to indicate which layers they thought
> were *un*maintained (since I assumed that list would be small), but this
> way works too.
>
> Interestingly enough, had I sorted the list on commit activity,
> according to http://git.yoctoproject.org/cgit/cgit.cgi/?s=idle
> meta-realtime hasn't been touched in 10 months which would make me
> suspect it was abandoned.
This approach is a good test of which layer maintainers are paying
attention to list traffic :)
Philip
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2014-01-10 1:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 18:45 unmaintained layers Trevor Woerner
2014-01-09 21:45 ` Bruce Ashfield
2014-01-09 22:43 ` Mark Hatle
2014-01-09 23:20 ` Trevor Woerner
2014-01-10 1:14 ` Philip Balister [this message]
2014-01-10 4:54 ` Bruce Ashfield
2014-01-10 5:47 ` Marko Lindqvist
2014-01-09 23:35 ` Martin Jansa
2014-01-10 1:23 ` Chris Larson
2014-01-10 4:50 ` Bruce Ashfield
2014-01-10 5:54 ` Andreas Müller
2014-01-10 6:29 ` Nathan Rossi
2014-01-10 7:03 ` Fathi Boudra
2014-01-10 7:08 ` Lukas Bulwahn
2014-01-10 7:21 ` Hongxu Jia
2014-01-10 13:20 ` Mario Schuknecht
2014-01-10 14:01 ` Paul Eggleton
2014-01-10 15:35 ` Koen Kooi
2014-01-10 15:51 ` Trevor Woerner
2014-01-10 16:02 ` Philip Balister
2014-01-10 16:24 ` Trevor Woerner
2014-01-10 16:28 ` Saul Wold
2014-01-10 17:27 ` Andrei Gherzan
2014-01-10 18:54 ` João Henrique Freitas
2014-01-12 20:28 ` Mike Looijmans
2014-01-12 20:42 ` Trevor Woerner
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=52CF4983.4070501@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=trevor.woerner@linaro.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