From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Armin Kuster <akuster808@gmail.com>
Cc: Armin Kuster <akuster@mvista.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] libassuan: update to 2.4.4
Date: Tue, 21 Nov 2017 17:56:34 +0200 [thread overview]
Message-ID: <58bea898-a1b0-3459-34b4-5e41490bdfd8@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZOr7EXUkH7J+_QSZzoKFOpobrExieEcAsNTQXNz0aXEA@mail.gmail.com>
On 11/21/2017 04:41 PM, Burton, Ross wrote:
> License checksum changes but no explanation.
Should we introduce a standard tag for the explanation, similar to cve tags?
License-checksum-change: copyright years updated
and then have the robot do the check, while we can spend time on more
interesting things.
Alex
next prev parent reply other threads:[~2017-11-21 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 0:07 [PATCH 0/5] Master package updates Armin Kuster
2017-11-21 0:07 ` [PATCH 1/5] gnutls: update to 3.6.1 Armin Kuster
2017-11-21 0:16 ` Andre McCurdy
2017-11-21 0:07 ` [PATCH 2/5] nettle: update to 3.4 and cleanup Armin Kuster
2017-11-21 0:07 ` [PATCH 3/5] nss: update to 3.34 Armin Kuster
2017-11-21 0:07 ` [PATCH 4/5] libassuan: update to 2.4.4 Armin Kuster
2017-11-21 14:41 ` Burton, Ross
2017-11-21 15:56 ` Alexander Kanavin [this message]
2017-11-21 16:08 ` akuster808
2017-11-21 0:07 ` [PATCH 5/5] curl: update to 7.56.1 Armin Kuster
2017-11-21 14:41 ` Burton, Ross
2017-11-21 0:35 ` ✗ patchtest: failure for Master package updates Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-11-21 20:01 [PATCH 0/5][V2] " Armin Kuster
2017-11-21 20:01 ` [PATCH 4/5] libassuan: update to 2.4.4 Armin Kuster
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=58bea898-a1b0-3459-34b4-5e41490bdfd8@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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