Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [daisy][PATCH 0/6] SRC_URI updates and minor build fixes
Date: Tue, 08 May 2018 10:15:20 +0100	[thread overview]
Message-ID: <1525770920.3857.109.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=UJUqrzyutyKf01HR1MDTN1YbYz+ovXkUTj+DARu1XW3w@mail.gmail.com>

On Tue, 2018-05-08 at 02:06 -0700, Andre McCurdy wrote:
> On Tue, May 8, 2018 at 12:40 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > We've discussed "long term" branches for a while. I suggest that we
> > collect together people who are will to maintain such things and
> > let
> > them push to a namespace in poky-contrib initially, perhaps in
> > other
> > repos eventually where we collect these things together.
> > 
> > Perhaps poky-contrib extended-life/daisy?
> > 
> > If there is common agreement, a group of people could collaborate
> > on such a branch too...
>
> Although there are multiple groups still actively developing against
> OE 1.6 I fear I may be the only one who has any interest in doing so
> in public. Hoping for a "group of people" to show up and collaborate
> on a branch in poky-contrib may be asking for too much.

Maybe, maybe not. I'd happy enough for you to put these changes there,
if others want to join in, great, if not I'm not sure we're in any
worse position. I just wanted to highlight the possibility in the
future...

Cheers,

Richard




  reply	other threads:[~2018-05-08  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21  2:42 [daisy][PATCH 0/6] SRC_URI updates and minor build fixes Andre McCurdy
2018-03-21  2:42 ` [daisy][PATCH 1/6] dtc: old SRC_URI died, changing to new working one Andre McCurdy
2018-03-21  2:42 ` [daisy][PATCH 2/6] kernel.bbclass: Remove bashism Andre McCurdy
2018-03-21  2:42 ` [daisy][PATCH 3/6] gmp_4.2.1: fix build for MIPS Andre McCurdy
2018-03-21  2:42 ` [daisy][PATCH 4/6] ncurses: fix build with gcc 5 Andre McCurdy
2018-03-21  2:42 ` [daisy][PATCH 5/6] binutils: " Andre McCurdy
2018-03-21  2:42 ` [daisy][PATCH 6/6] mesa: fix SRC_URI Andre McCurdy
2018-05-08  1:22 ` [daisy][PATCH 0/6] SRC_URI updates and minor build fixes Andre McCurdy
2018-05-08  7:40   ` Richard Purdie
2018-05-08  9:06     ` Andre McCurdy
2018-05-08  9:15       ` Richard Purdie [this message]
2018-05-08 22:07         ` Andre McCurdy
2018-05-09 11:09           ` Richard Purdie
2018-05-10  4:36             ` Andre McCurdy

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=1525770920.3857.109.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox