mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-08-25 19:21:53 +00:00
docs: Fix typos and formatting
Correct spelling mistakes and formatting issues. Fixes: #107. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
This commit is contained in:
parent
7047db1084
commit
c829871650
@ -12,7 +12,7 @@ serve as a short introduction and reminder of the basic stable backport process.
|
|||||||
## Backport Workflow
|
## Backport Workflow
|
||||||
|
|
||||||
The basic workflow involves creating a new local branch from the stable tree you
|
The basic workflow involves creating a new local branch from the stable tree you
|
||||||
are targetting, then cherry picking the commits from your master branch PR
|
are targeting, then cherry picking the commits from your master branch PR
|
||||||
onto that branch. You then submit your branch to GitHub as a PR against the
|
onto that branch. You then submit your branch to GitHub as a PR against the
|
||||||
stable branch (and not the `master` branch).
|
stable branch (and not the `master` branch).
|
||||||
|
|
||||||
|
@ -803,7 +803,7 @@ Some of the checks are:
|
|||||||
- Static analysis checks.
|
- Static analysis checks.
|
||||||
- Unit tests.
|
- Unit tests.
|
||||||
- Functional tests.
|
- Functional tests.
|
||||||
- Integretation tests.
|
- Integration tests.
|
||||||
|
|
||||||
The Travis job will be executed right after the PR is opened, while the Jenkins
|
The Travis job will be executed right after the PR is opened, while the Jenkins
|
||||||
jobs will wait to be triggered. A maintainer must add a `/test` comment
|
jobs will wait to be triggered. A maintainer must add a `/test` comment
|
||||||
|
10
README.md
10
README.md
@ -73,11 +73,11 @@ The Architecture Committee is responsible for architectural decisions, including
|
|||||||
|
|
||||||
The current Architecture Committee members are:
|
The current Architecture Committee members are:
|
||||||
|
|
||||||
- Eric Ernst ([`egernst`](https://github.com/egernst)), [Intel](https://www.intel.com/).
|
- `Eric Ernst` ([`egernst`](https://github.com/egernst)), [Intel](https://www.intel.com/).
|
||||||
- Samuel Ortiz ([`sameo`](https://github.com/sameo)), [Intel](https://www.intel.com).
|
- `Samuel Ortiz` ([`sameo`](https://github.com/sameo)), [Intel](https://www.intel.com).
|
||||||
- Jon Olson ([`jon`](https://github.com/jon)), [Google](https://www.google.com).
|
- `Jon Olson` ([`jon`](https://github.com/jon)), [Google](https://www.google.com).
|
||||||
- Xu Wang ([`gnawux`](https://github.com/gnawux)), [Ant Financial](https://www.antfin.com/index.htm?locale=en_US).
|
- `Xu Wang` ([`gnawux`](https://github.com/gnawux)), [Ant Financial](https://www.antfin.com/index.htm?locale=en_US).
|
||||||
- Zhang Wei ([`WeiZhang555`](https://github.com/WeiZhang555)), [Huawei](http://www.huawei.com).
|
- `Zhang Wei` ([`WeiZhang555`](https://github.com/WeiZhang555)), [Huawei](http://www.huawei.com).
|
||||||
|
|
||||||
Architecture Committee elections take place in September (3 seats available) and February (2 seats available). Anyone who has made contributions to the project will be eligible to run, and anyone who has had code merged into the Kata Containers project in the 12 months (a Contributor) before the election will be eligible to vote. There are no term limits, but in order to encourage diversity, no more than 2 of the 5 seats can be filled by any one organization. The Architecture Committee will meet regularly in an open forum with times and locations published in community channels.
|
Architecture Committee elections take place in September (3 seats available) and February (2 seats available). Anyone who has made contributions to the project will be eligible to run, and anyone who has had code merged into the Kata Containers project in the 12 months (a Contributor) before the election will be eligible to vote. There are no term limits, but in order to encourage diversity, no more than 2 of the 5 seats can be filled by any one organization. The Architecture Committee will meet regularly in an open forum with times and locations published in community channels.
|
||||||
|
|
||||||
|
@ -2,7 +2,7 @@ announcement-date: 2019-02-22
|
|||||||
|
|
||||||
id: KCSA-CVE-2019-5736
|
id: KCSA-CVE-2019-5736
|
||||||
|
|
||||||
title: CVE-2019-5736 "runc container breakout" assessment
|
title: CVE-2019-5736 `runc container breakout` assessment
|
||||||
|
|
||||||
description: Impact of CVE-2019-5736 on Kata Containers
|
description: Impact of CVE-2019-5736 on Kata Containers
|
||||||
|
|
||||||
@ -13,11 +13,11 @@ potentially-affected-components:
|
|||||||
|
|
||||||
vulnerabilities:
|
vulnerabilities:
|
||||||
|
|
||||||
- cve-id: CVE-2019-5736
|
- CVE-ID: CVE-2019-5736
|
||||||
|
|
||||||
reporters:
|
reporters:
|
||||||
|
|
||||||
- name: Graham Whaley
|
- name: `Graham Whaley`
|
||||||
affiliation: VMT member
|
affiliation: VMT member
|
||||||
reported:
|
reported:
|
||||||
- Original report seen on dev@opencontainers.org
|
- Original report seen on dev@opencontainers.org
|
||||||
|
Loading…
Reference in New Issue
Block a user