From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for "boost: fix upstream version ch..." and 3 more
Date: Mon, 24 Apr 2017 16:32:54 +0300 [thread overview]
Message-ID: <ec6e5aa6-1584-7a9f-713f-23fb90f737d4@linux.intel.com> (raw)
In-Reply-To: <20170424133158.26296.93393@do.openembedded.org>
On 04/24/2017 04:31 PM, Patchwork wrote:
> * Issue Series does not apply on top of target branch [test_series_merge_on_head]
> Suggested fix Rebase your series on top of targeted branch
> Targeted branch master (currently at e584be78f9)
Yep; this was meant for ross/mut where patches are currently being
accumulated.
Alex
prev parent reply other threads:[~2017-04-24 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 13:15 [PATCH 1/4] boost: fix upstream version check Alexander Kanavin
2017-04-24 13:15 ` [PATCH 2/4] libproxy: speed up " Alexander Kanavin
2017-04-24 13:15 ` [PATCH 3/4] portmap: remove recipe Alexander Kanavin
2017-04-24 13:15 ` [PATCH 4/4] linux-libc-headers: fix upstream version check Alexander Kanavin
2017-04-24 13:31 ` ✗ patchtest: failure for "boost: fix upstream version ch..." and 3 more Patchwork
2017-04-24 13:32 ` Alexander Kanavin [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=ec6e5aa6-1584-7a9f-713f-23fb90f737d4@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox