All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bbappend
Date: Tue, 12 Jul 2011 15:18:50 +0100	[thread overview]
Message-ID: <201107121518.51033.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <20110712140847.GA788@cverges-dev-lnx>

On Tuesday 12 July 2011 15:08:47 Chris Verges wrote:
> Thanks for clarifying and proposing a workaround.  It looks like PRINC
> is similar, where it is only available in oe-core.  It seems like the
> code related to incrementing the PR variable is a several-line fix, so
> is this something that can be abstracted into a class file in the
> local-overlay?

Possibly, however as a general suggestion I would recommend moving things over 
to being based on oe-core if at all possible. I realise this is not going to 
be practical for everyone in the short term, however OE classic will stop 
being maintained at some point in the near future, so the sooner you move the 
better - plus you get to take advantage of the additional features and 
cleanups in oe-core as well.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-07-12 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  8:58 bbappend Jaap de Jong
2011-07-12  8:58 ` bbappend Jaap de Jong
2011-07-12  9:42   ` bbappend Paul Eggleton
2011-07-12 14:08     ` bbappend Chris Verges
2011-07-12 14:18       ` Paul Eggleton [this message]
2011-07-12 14:31         ` bbappend Chris Verges
2011-07-12 14:56           ` bbappend Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2011-09-30  6:03 bbappend Jaap de Jong

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=201107121518.51033.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --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 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.