From: Ross Burton <ross.burton@intel.com>
To: Ferry Toth <fntoth@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for sudo: Fix fetching sources
Date: Mon, 28 Oct 2019 21:36:34 +0000 [thread overview]
Message-ID: <66c4f274-4174-f3d2-53dc-5aed60ace3bf@intel.com> (raw)
In-Reply-To: <d4f5d7f5-a72d-7602-0ed7-b77821609f28@gmail.com>
On 25/10/2019 21:39, Ferry Toth wrote:
> Op 25-10-2019 om 21:32 schreef Patchwork:
>> == Series Details ==
>>
>> Series: sudo: Fix fetching sources
>> Revision: 1
>> URL : https://patchwork.openembedded.org/series/20684/
>> State : failure
>>
>> == Summary ==
>>
>>
>> Thank you for submitting this patch series to OpenEmbedded Core. This is
>> an automated response. Several tests have been executed on the proposed
>> series by patchtest resulting in the following failures:
>>
>>
>>
>> * 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 1a8d18eeee)
>>
>>
>>
>> If you believe any of these test results are incorrect, please reply
>> to the
>> mailing list (openembedded-core@lists.openembedded.org) raising your
>> concerns.
>> Otherwise we would appreciate you correcting the issues and submitting
>> a new
>> version of the patchset if applicable. Please ensure you add/increment
>> the
>> version number when sending the new version (i.e. [PATCH] -> [PATCH
>> v2] ->
>> [PATCH v3] -> ...).
>
> The patch applies to thud.
But the patch doesn't say [thud] in the subject so nobody else knows
this, and the patch process says we fix master, then zeus, then warrior,
then thud.
Ross
next prev parent reply other threads:[~2019-10-28 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 19:12 [PATCH] sudo: Fix fetching sources Ferry Toth
2019-10-25 19:32 ` ✗ patchtest: failure for " Patchwork
2019-10-25 20:39 ` Ferry Toth
2019-10-28 21:36 ` Ross Burton [this message]
2019-10-28 23:07 ` Ferry Toth
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=66c4f274-4174-f3d2-53dc-5aed60ace3bf@intel.com \
--to=ross.burton@intel.com \
--cc=fntoth@gmail.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