All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Larson <kergoth@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] patch.bbclass: abstract out logic that determines patches to apply
Date: Tue, 27 Dec 2011 20:18:07 -0700	[thread overview]
Message-ID: <C912F71A353F438184732085CC1952DC@gmail.com> (raw)
In-Reply-To: <CABcZAN=kQT-imznF0wRWW_Nazs+YefcC2YY-yk+ckp6gjV757w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

Pushed an updated version of the patch-refactor commit that should fix this.
-- 
Christopher Larson


On Tuesday, December 27, 2011 at 1:38 PM, Chris Larson wrote:

> On Tue, Dec 27, 2011 at 1:33 PM, Saul Wold <sgw@linux.intel.com (mailto:sgw@linux.intel.com)> wrote:
> > Do you need to pass d here?
> > 
> > I am seeing errors (see
> > http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/295/steps/shell_14/logs/stdio)
> > 
> 
> 
> Bah, indeed, apparently my testing didn't hit any recipes using
> minrev/maxrev/notrev. Will rework the patch. Grr.
> 
> 


[-- Attachment #2: Type: text/html, Size: 1166 bytes --]

  reply	other threads:[~2011-12-28  3:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 17:38 [PATCH] patch.bbclass: abstract out logic that determines patches to apply Christopher Larson
2011-12-20 18:28 ` Bruce Ashfield
2011-12-21 17:24 ` Richard Purdie
2011-12-27 17:31   ` Chris Larson
2011-12-27 20:33 ` Saul Wold
2011-12-27 20:38   ` Chris Larson
2011-12-28  3:18     ` Christopher Larson [this message]
2012-01-03 23:52       ` Saul Wold

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=C912F71A353F438184732085CC1952DC@gmail.com \
    --to=kergoth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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.