From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Ovidiu Panait <ovidiu.panait@windriver.com>
Subject: Re: ✗ patchtest: failure for git: CVE-2017-14867
Date: Mon, 23 Oct 2017 14:22:14 -0500 [thread overview]
Message-ID: <1508786534.11251.2@fm-out.intel.com> (raw)
In-Reply-To: <20171023180300.2784.27290@do.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
>
>
>
> * Issue LIC_FILES_CHKSUM changed on target git but there
> was no explanation as to why in the commit message
> [test_lic_files_chksum_modified_not_mentioned]
> Suggested fix Provide a reason for LIC_FILES_CHKSUM change in
> commit message
> Current checksum
> New checksum file://COPYING;md5=7c0d7ef03a7eb04ce795b0f60e68e7e1
This is a bad check from patchtest (so ignore this complain). CCing
Daniela, she is currently reviewing these issues.
Leo
[-- Attachment #2: Type: text/html, Size: 811 bytes --]
next prev parent reply other threads:[~2017-10-23 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 17:39 [PATCH] git: CVE-2017-14867 Ovidiu Panait
2017-10-23 18:03 ` ✗ patchtest: failure for " Patchwork
2017-10-23 19:22 ` Leonardo Sandoval [this message]
2017-10-24 9:01 ` [PATCH] " Alexander Kanavin
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=1508786534.11251.2@fm-out.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ovidiu.panait@windriver.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