From: akuster808 <akuster808@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>, poky@yoctoproject.org
Subject: Re: [PATCH] nettle: add nettle to tracking
Date: Thu, 21 Aug 2014 15:10:48 -0700 [thread overview]
Message-ID: <53F66E68.8050707@gmail.com> (raw)
In-Reply-To: <53F66A63.6070206@mlbassoc.com>
On 08/21/2014 02:53 PM, Gary Thomas wrote:
> On 2014-08-21 15:46, Armin Kuster wrote:
>> add not regarding nettle upgrade
>>
>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>> meta-yocto/conf/distro/include/upstream_tracking.inc | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/meta-yocto/conf/distro/include/upstream_tracking.inc
>> b/meta-yocto/conf/distro/include/upstream_tracking.inc
>> index a018803..ab94ac4 100644
>> --- a/meta-yocto/conf/distro/include/upstream_tracking.inc
>> +++ b/meta-yocto/conf/distro/include/upstream_tracking.inc
>> @@ -162,6 +162,8 @@ CHECK_DATE_pn-module-init-tools = "Aug 31, 2012"
>> RECIPE_UPSTREAM_DATE_pn-modutils-initscripts = "n/a"
>> RECIPE_NO_UPDATE_REASON_pn-mpeg2dec = "Why are we currently at 0.4.1?"
>> RECIPE_NO_UPDATE_REASON_pn-mx-1.0 = "PRS 1.99 is dev version"
>> +CHECK_DATE_pn-nettle = "Aug 21, 2014"
>> +RECIPE_NO_UPDATE_REASON-nettle = "3.0.0 breaks gnutls, api changes"
>
> Shouldn't this be RECIPE_NO_UPDATE_REASON_pn-nettle?
sigh, yeah..
will fix.
should also add,
RECIPE_NO_UPDATE_REASON_pn-akuster = "prone to brain farts "
>
>> RECIPE_UPSTREAM_VERSION_pn-ofono = "1.6"
>> RECIPE_UPSTREAM_DATE_pn-ofono="Apr 20, 2012"
>> CHECK_DATE_pn-ofono = "Aug 31, 2012"
>>
>
prev parent reply other threads:[~2014-08-21 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 21:46 [PATCH] nettle: add nettle to tracking Armin Kuster
2014-08-21 21:53 ` Gary Thomas
2014-08-21 22:10 ` akuster808 [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=53F66E68.8050707@gmail.com \
--to=akuster808@gmail.com \
--cc=gary@mlbassoc.com \
--cc=poky@yoctoproject.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.