Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gpgme: add GPGME_STATUS_KEY_CONSIDERED
Date: Thu, 22 Dec 2016 10:24:59 +0800	[thread overview]
Message-ID: <585B397B.6080206@windriver.com> (raw)
In-Reply-To: <f00958f8-1c4a-e0ae-8a13-d6f672c8a850@linux.intel.com>



On 2016年12月21日 20:25, Alexander Kanavin wrote:
> On 12/21/2016 01:14 PM, Burton, Ross wrote:
>>
>> https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=315fb73d4a774e2c699ac1804f5377559b4d0027
>>
>>
>> <https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=315fb73d4a774e2c699ac1804f5377559b4d0027>
>>
>>
>>
>> Can you explain *why* we should cherry pick a patch from upstream?
>
> Because someone didn't check RRS, which would suggest an update to gpgme
> 1.8.0 should be done instead.
>
> http://recipes.yoctoproject.org/rrs/recipedetail/834/


Thanks Alex!
Actually I ever tried to upgrade gpgme to 1.8.0 before send out this 
patch, but there comes other ptest failed issues for python-pygpgme 
which not exist on current gpgme 1.6.0 if we simply update gpgme to 1.8.0.

Anyway I prefer to wait for more update for python-pygpgme from 
https://pagure.io/pygpgme/commits/master before we move forward to gpgme 
1.8.0.

Thanks,
Mingli

>
> Alex
>
>


  reply	other threads:[~2016-12-22  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  8:19 [PATCH] gpgme: add GPGME_STATUS_KEY_CONSIDERED mingli.yu
2016-12-21 11:14 ` Burton, Ross
2016-12-21 12:25   ` Alexander Kanavin
2016-12-22  2:24     ` Yu, Mingli [this message]
2016-12-22 14:30       ` Alexander Kanavin
2016-12-22  1:52   ` Yu, Mingli

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=585B397B.6080206@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=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