Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Discussion of the angstrom distribution development
	<angstrom-distro-devel@linuxtogo.org>
Cc: Koen Kooi <k.kooi@student.utwente.nl>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [Angstrom-devel] [PATCH] sane-feed.inc: adding some ATMEL boards
Date: Tue, 12 Jan 2010 09:26:59 +0100	[thread overview]
Message-ID: <4B4C3253.7040702@atmel.com> (raw)
In-Reply-To: <hiflqc$b75$1@ger.gmane.org>

Le 11/01/2010 18:06, Koen Kooi :
> On 11-01-10 16:45, Nicolas Ferre wrote:
>> Add some armv5te entries for ATMEL -EK boards.
> 
> FEED_ARCH is deprecated and shouldn't be used any more. I'm surprised it
> spread beyond angstrom after it being deprecated, but I guess that's
> what blind copy-pasting will do for you.

Ok then.

Bye,
-- 
Nicolas Ferre




      parent reply	other threads:[~2010-01-12  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 15:45 [PATCH] sane-feed.inc: adding some ATMEL boards Nicolas Ferre
     [not found] ` <hiflqc$b75$1@ger.gmane.org>
2010-01-12  8:26   ` Nicolas Ferre [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=4B4C3253.7040702@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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