From: Daiane Angolini <daiane.angolini@freescale.com>
To: "Lewis, Nick" <nick.lewis@usa.g4s.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
'Otavio Salvador' <otavio@ossystems.com.br>
Subject: Re: user layer problem with udev_173.bbappend
Date: Thu, 18 Apr 2013 08:47:41 -0300 [thread overview]
Message-ID: <516FDD5D.7010908@freescale.com> (raw)
In-Reply-To: <AAE0766F5AF36B46BAB7E0EFB927320630E4A540AE@GBTWK10E001.Technology.local>
On 04/18/2013 05:08 AM, Lewis, Nick wrote:
>> Yes, we can use 'VAR +=' but the biggest problem is why you need to override it.
>
> Generally speaking there may be any number of reasons by a client layer may want to override something in the meta-fsl layer or another serving layer.
> 'VAR_prepend =' breaks the whole layering concept. For this reason alone I ask that it be replaced
>
I agree and I think it's a good reason.
Could you, please, send the patch?
(and please, use git and git format-patch to create your patch. and git
send-email to sent your patch)
Otavio, how long danny will be supported after dylan being released?
What's the "usual way"?
Daiane
next prev parent reply other threads:[~2013-04-18 11:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 14:43 user layer problem with udev_173.bbappend Lewis, Nick
2013-04-16 14:54 ` Angolini Daiane-B19406
2013-04-16 15:03 ` Lewis, Nick
2013-04-16 15:12 ` Lewis, Nick
2013-04-16 15:27 ` Fabio Estevam
2013-04-16 15:45 ` Lewis, Nick
2013-04-16 16:35 ` Angolini Daiane-B19406
2013-04-17 7:28 ` Lewis, Nick
2013-04-17 9:58 ` Lewis, Nick
2013-04-17 11:15 ` Lewis, Nick
2013-04-17 17:19 ` Otavio Salvador
2013-04-18 8:08 ` Lewis, Nick
2013-04-18 8:14 ` Lewis, Nick
2013-04-18 11:47 ` Daiane Angolini [this message]
2013-04-18 12:17 ` Otavio Salvador
2013-04-18 13:09 ` Lewis, Nick
2013-04-18 13:18 ` Otavio Salvador
2013-04-19 8:54 ` Lewis, Nick
2013-04-19 11:57 ` Otavio Salvador
2013-04-19 13:11 ` Lewis, Nick
2013-04-19 13:21 ` Otavio Salvador
2013-04-18 12:00 ` Otavio Salvador
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=516FDD5D.7010908@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=nick.lewis@usa.g4s.com \
--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.