All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yannick Calmettes <yannick.calmettes@analogway.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: imx-3.10.31-1.1.0_beta : Can't build meta-toolchain-qt5
Date: Wed, 17 Dec 2014 18:46:59 +0100	[thread overview]
Message-ID: <5491C193.4020908@analogway.com> (raw)
In-Reply-To: <CAP9ODKq5NkLDg3pBtiyaLr0ypL3rY64VSu0Fieroii+ywNg1PQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

Thank you Otavio, it's interesting to know in which conditions we can be 
supported.

Regards,

Yannick
**
Le 17/12/2014 17:58, Otavio Salvador a écrit :
> On Wed, Dec 17, 2014 at 1:47 PM, Yannick Calmettes
> <yannick.calmettes@analogway.com> wrote:
>> Thanks Otavio but if I want support from Freescale I have to use "stuck"
>> revisions. I use today the Beta because normally the release will come
>> before my product first release.
> As soon you add your custom board on top of it, you are not
> "supported" as they will ask you to reproduce in their reference
> boards.
>
> Please take a look at:
>
> http://freescale.github.io/doc/release-notes/1.7/index.html#the-differences-between-project-name-and-freescale-release-name
>


 

[-- Attachment #2: Type: text/html, Size: 2300 bytes --]

  reply	other threads:[~2014-12-17 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 13:32 imx-3.10.31-1.1.0_beta : Can't build meta-toolchain-qt5 Yannick Calmettes
2014-12-17 14:25 ` Eric Bénard
2014-12-17 15:14   ` Yannick Calmettes
2014-12-17 15:28 ` Otavio Salvador
2014-12-17 15:47   ` Yannick Calmettes
2014-12-17 16:58     ` Otavio Salvador
2014-12-17 17:46       ` Yannick Calmettes [this message]
2014-12-18 14:11         ` Lauren Post

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=5491C193.4020908@analogway.com \
    --to=yannick.calmettes@analogway.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.