Merge ~mainek00n/ubuntu-cve-tracker:patch-1 into ubuntu-cve-tracker:master
Proposed by
MaineK00n
Status: | Merged |
---|---|
Merged at revision: | 6af7e65807722faba358be272b98960528d6ea9c |
Proposed branch: | ~mainek00n/ubuntu-cve-tracker:patch-1 |
Merge into: | ubuntu-cve-tracker:master |
Diff against target: |
116 lines (+8/-7) 10 files modified
active/CVE-2018-12294 (+1/-0) active/CVE-2021-23214 (+0/-1) active/CVE-2021-23222 (+0/-1) active/CVE-2022-1552 (+0/-2) retired/CVE-2007-4351 (+1/-1) retired/CVE-2008-4098 (+1/-1) retired/CVE-2010-1850 (+2/-0) retired/CVE-2011-1837 (+1/-0) retired/CVE-2012-0809 (+1/-0) retired/CVE-2012-3410 (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Steve Beattie | Approve | ||
Review via email: mp+427960@code.launchpad.net |
To post a comment you must log in.
LGTM, merged.
One note, for the sudo cve, that issue was discovered and resolved while precise was under development and had not been released yet. When we retire a cve, we don't turn the `devel` status into the release name under development, so that results in things like this.