Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Add Freescale P2020DS Demo Board
Date: Wed, 10 Mar 2010 15:59:06 +0100	[thread overview]
Message-ID: <hn8c3q$o8a$2@dough.gmane.org> (raw)
In-Reply-To: <201003101549.01069.marcin@juszkiewicz.com.pl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10-03-10 15:49, Marcin Juszkiewicz wrote:
> Dnia środa, 10 marca 2010 o 15:36:48 Martyn Welch napisał(a):
>> Marcin Juszkiewicz wrote:
> 
>>> OE policy is to keep defconfig inside of OE tree. Please add
>>> mpc85xx_defconfig as recipes/linux/linux-2.6.33/p2020ds/defconfig and
>>> resubmit.
>>
>> Will do. 
> 
>> Out of interest, what's the rationale for this?
> 
> Maintainers of OE derived distributions can provide own configs for target 
> devices.

Without going to patching hell I must add :) It allows people to cp
.config foo/bar/defconfig instead of doing patches on top of patches.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLl7O6MkyGM64RGpERAvT/AJ0U0D7pk1jY1YYgdYKdIsuYG8nAsQCgtG0T
Xj10isiDz61djIU6Db3qFnY=
=lWvX
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-03-10 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 13:54 [PATCH] Add Freescale P2020DS Demo Board Martyn Welch
2010-03-10 14:08 ` Marcin Juszkiewicz
2010-03-10 14:36   ` Martyn Welch
2010-03-10 14:49     ` Marcin Juszkiewicz
2010-03-10 14:59       ` Koen Kooi [this message]
2010-03-10 15:29 ` Tom Rini
2010-03-10 15:54   ` Martyn Welch
2010-03-10 16:08     ` Martyn Welch
2010-03-10 16:32       ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2010-03-10 16:47 Martyn Welch
2010-03-10 16:51 ` Tom Rini

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='hn8c3q$o8a$2@dough.gmane.org' \
    --to=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