summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Mosbarger <ericx.mosbarger@intel.com>2020-12-07 21:20:56 +0300
committerEric Mosbarger <ericx.mosbarger@intel.com>2020-12-07 21:20:56 +0300
commitef8213d56914a3cbab7782ca7f1dfe3b10d6b95b (patch)
tree7904ed6080b1a9ee534b9ef832f432dc0dcf0d08
parent73c8511c16ea4a7a89ef39103344ac6a8ecd4293 (diff)
downloadopenbmc-ef8213d56914a3cbab7782ca7f1dfe3b10d6b95b.tar.xz
Fake change 111
-rw-r--r--README.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/README.md b/README.md
index 5d611f5f1..a13a2d7f2 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ https://github.com/Intel-BMC/validation_results/blob/master/README.md
### Does this mean that Intel, Corp, is no longer contributing to the Linux Foundation (LF) project?
-Nope. This repo is for components that are intended for eventual release to
+No. This repo is for components that are intended for eventual release to
the LF OpenBMC project. There are a number of reasons where things
might be checked in here. For example: functionality that is still under
discussion or in the LF OpenBMC project, features that have not gone through
@@ -26,14 +26,14 @@ project
### Why does this repo exist ?
-Upstreaming changes to the linux kernel, uboot, systemd, yocto, and the various
-projects that OpenBMC pulls in requires a significant effort. While we aspire
-to process quickly, painlessly, and with minimal rework, the reality is
-far from that. Features or functions that require changes across a number
-of repos require a coordinated effort, and a single source of function. As a
-general rule, this repository loosens the requirements of "form over function"
-and prefers to make some simplifying assumptions of BMC capabilities, chipsets,
-and required features.
+Upstreaming changes to the linux kernel, uboot, systemd, yocto, and the
+various projects that OpenBMC pulls in requires a significant effort.
+While we aspire to process quickly, painlessly, and with minimal rework,
+the reality is far from that. Features or functions that require changes
+across a number of repos require a coordinated effort, and a single source of
+function. As a general rule, this repository loosens the requirements of
+"form over function" and prefers to make some simplifying assumptions of
+BMC capabilities, chipsets, and required features.
### Can I upstream/release code from this repository?