All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: edison/denzil patches (post-1.1.2 and 1.2.1)
Date: Mon, 16 Jul 2012 07:58:14 -0700	[thread overview]
Message-ID: <50042C06.70900@linux.intel.com> (raw)
In-Reply-To: <CAEsOVNehMk8dmo2O+MpOfs0JM9OPARB2Jd+dzTFw0g93SHYcyA@mail.gmail.com>

On 12/07/12 10:43, McClintock Matthew-B29882 wrote:
> Josh, Scott:
>
> I've pushed a set of patches for edison/denzil branch - and I may push
> a few more still to:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mattsm/edison
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mattsm/denzil
>
> These are all cherry-pick's and most applied cleanly and a few had
> some minor cleanups. Please consider these for after the point
> releases. I will continue to push to these branches and rebase these
> branches off the official upstream trees as well.

I don't know how much work will be done on Edison after the 1.1.2 
release. I personally will no longer be working on it and I don't think 
the team here as enough resources to maintain it perpetually.

I assume that these changes are predominantly to further improve PPC 
support?

In general your branch has several types of changes that have generally 
been considered inappropriate for a point release (such as recipe 
upgrades, new functionality, etc).

Personally I'm not very keen on the idea of pushing them all and 
advocating their inclusion. I'd strongly encourage adoption of this 
release series if it's to continue to be relevant to your work.

Cheers,
Joshua
-- 
Joshua Lock
         Intel Open Source Technology Centre




  parent reply	other threads:[~2012-07-16 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 17:43 edison/denzil patches (post-1.1.2 and 1.2.1) McClintock Matthew-B29882
2012-07-12 18:55 ` McClintock Matthew-B29882
2012-07-16 14:58 ` Joshua Lock [this message]
2012-07-16 15:10   ` McClintock Matthew-B29882
2012-07-16 15:32     ` Joshua Lock
2012-07-16 16:01       ` McClintock Matthew-B29882
2012-07-16 16:34         ` Joshua Lock
2012-07-17 20:18         ` Stewart, David C
2012-07-17 20:43           ` McClintock Matthew-B29882
2012-07-17 21:19             ` William Mills
2012-07-23 19:59               ` McClintock Matthew-B29882
2012-08-13 13:43                 ` David Nyström
2012-07-16 16:22 ` Scott Garman
2012-07-16 16:25   ` McClintock Matthew-B29882

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=50042C06.70900@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=B29882@freescale.com \
    --cc=yocto@yoctoproject.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.