diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-05-20 18:14:37 +0100 |
---|---|---|
committer | Steve Sakoman <steve@sakoman.com> | 2021-05-28 14:22:21 -1000 |
commit | 43d8d7001402aebc78979f3c86493f0aa15140a4 (patch) | |
tree | 974c1a9056ae5b4f6bfa46157f4b17a1e01e8b44 /meta/conf | |
parent | c93d541a84ce4f9ed52b7aee0a59857957ea0380 (diff) | |
download | openembedded-core-43d8d7001402aebc78979f3c86493f0aa15140a4.tar.gz |
cve-extra-exclusions: Fix typos
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit d4d4644e7c127e8b88b180635124e8afc905c69e)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'meta/conf')
-rw-r--r-- | meta/conf/distro/include/cve-extra-exclusions.inc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/meta/conf/distro/include/cve-extra-exclusions.inc b/meta/conf/distro/include/cve-extra-exclusions.inc index 565c8e04cc..b2816c3dd5 100644 --- a/meta/conf/distro/include/cve-extra-exclusions.inc +++ b/meta/conf/distro/include/cve-extra-exclusions.inc @@ -1,17 +1,17 @@ # This file contains a list of CVE's where resolution has proven to be impractical -# or there is no reasonable action the Yocto Project can take to resovle the issue. +# or there is no reasonable action the Yocto Project can take to resolve the issue. # It contains all the information we are aware of about an issue and analysis about # why we believe it can't be fixed/handled. Additional information is welcome through # patches to the file. # # Include this file in your local.conf or distro.conf to exclude these CVE's # from the cve-check results or add to the bitbake command with: -# -R meta/conf/distro/include/cve-extra-exclusions.inc +# -R conf/distro/include/cve-extra-exclusions.inc # # The file is not included by default since users should review this data to ensure -# it matches their expectations and ussage of the project. +# it matches their expectations and usage of the project. # -# Wemay also include "in-flight" information about current/ongoing CVE work with +# We may also include "in-flight" information about current/ongoing CVE work with # the aim of sharing that work and ensuring we don't duplicate it. # |