From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lib/oe/patch.py: Fix patch resolver logic
Date: Fri, 02 Mar 2012 12:20:22 +0000 [thread overview]
Message-ID: <1330690822.15224.12.camel@ted> (raw)
In-Reply-To: <1330645282.15224.0.camel@ted>
On Thu, 2012-03-01 at 23:41 +0000, Richard Purdie wrote:
> Currently, if PATCHRESOLVE is user and and PatchTree() is being used, you can
> get backtraces if patch applcication fails. This is because even in the failure
> case, self._current is incremented, meaning second time around, there are array
> range issues.
>
> This patch changes the code so _current is only incremented upon successful
> patch application, thereby resolving this failure.
>
> [YOCTO #2043 partially]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch is wrong, it breaks with multiple patch application. I've
posted an updated patch.
Cheers,
Richard
prev parent reply other threads:[~2012-03-02 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 23:41 [PATCH] lib/oe/patch.py: Fix patch resolver logic Richard Purdie
2012-03-02 12:20 ` Richard Purdie [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=1330690822.15224.12.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.