From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] classes/patch: avoid backtrace when patch does not apply
Date: Thu, 19 Jan 2012 14:32:23 +0000 [thread overview]
Message-ID: <1326983543.2511.71.camel@ted> (raw)
In-Reply-To: <592d932934f891f3f73dc9630fa9d1a7d94aff56.1326981479.git.paul.eggleton@linux.intel.com>
On Thu, 2012-01-19 at 13:59 +0000, Paul Eggleton wrote:
> We don't need to see a Python stack backtrace when a patch does not
> apply, just the error output from patch, so trap these kinds of errors
> and ensure that we display the message and fail the task and nothing
> else.
>
> Fixes [YOCTO #1143]
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> meta/classes/patch.bbclass | 5 ++++-
> meta/lib/oe/patch.py | 10 +++++-----
> 2 files changed, 9 insertions(+), 6 deletions(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-01-19 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 13:59 [PATCH 0/2] Misc fixes Paul Eggleton
2012-01-19 13:59 ` [PATCH 1/2] classes/patch: avoid backtrace when patch does not apply Paul Eggleton
2012-01-19 14:32 ` Richard Purdie [this message]
2012-01-19 13:59 ` [PATCH 2/2] hdparm: remove PRIORITY Paul Eggleton
2012-01-19 14:32 ` Richard Purdie
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=1326983543.2511.71.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.