Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sip-native: Run oe-stylize script on the recipe and modify the recipe accordingly.
Date: Thu, 02 Sep 2010 01:10:07 +0200	[thread overview]
Message-ID: <1283382607.2012.25.camel@saphir> (raw)
In-Reply-To: <4C7EDCD7.3030300@mentor.com>

Am Mittwoch, den 01.09.2010, 16:08 -0700 schrieb Tom Rini:
> > I like to keep a mental model of recipes being somewhat executed in a
> > top-down manner; in the model, exported variable assignments do in fact
> > affect all of tasks, so I think they should be kept next to the
> > non-exported assignments.
> 
> Yes, that does sound right, fixing oe-stylize now...

Splendid! Thanks a lot.

-- 
:M:




      reply	other threads:[~2010-09-01 23:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 16:02 [PATCH] sip-native: Run oe-stylize script on the recipe and modify the recipe accordingly Noor Ahsan
2010-09-01 19:41 ` Frans Meulenbroeks
2010-09-01 23:05   ` Michael 'Mickey' Lauer
2010-09-01 23:00 ` Michael 'Mickey' Lauer
2010-09-01 23:08   ` Tom Rini
2010-09-01 23:10     ` Michael 'Mickey' Lauer [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=1283382607.2012.25.camel@saphir \
    --to=mickey@vanille-media.de \
    --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