All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@openedhand.com>
To: poky@yoctoproject.org
Subject: Re: Poky Laverne point release
Date: Mon, 10 Jan 2011 18:13:15 +0000	[thread overview]
Message-ID: <1294683195.2451.12.camel@scimitar> (raw)
In-Reply-To: <1292872200.2466.58.camel@scimitar>

On Mon, 2010-12-20 at 19:10 +0000, Joshua Lock wrote:
> Hi all,
> 
> I've a branch on poky-contrib (josh/laverne) which fixes the Makefiles
> in several recipes such that I can do builds of all our targets on
> Fedora 14 with it's new, stricter, make version (3.82).
> 
> This makes me think it's time to start pulling together a Laverne point
> release but we don't really have a handle on what these should include.
> 
> For the Green point release I cooked I just went through commits since
> the release and did sniff testing, but I think we can do better.
> Plus I started to do that for Laverne but there's been some almost 900
> commits since then... 
> 
> So, to the point of this message, I'm looking for people to nominate
> fixes for the Laverne branch. Even better if you share a git hash.
> 
> To start the ball rolling I'm going to suggest:
> * Make 3.82 fixes
> * Qemu script enhancements/fixes
> * Bitbake fetcher fixes
> 
> 
> And you? What fixes would you suggest?

<gentle nudge for feedback>

I guess we don't have many users of Laverne?

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



      reply	other threads:[~2011-01-10 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 19:10 Poky Laverne point release Joshua Lock
2011-01-10 18:13 ` Joshua Lock [this message]

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=1294683195.2451.12.camel@scimitar \
    --to=josh@openedhand.com \
    --cc=poky@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.