Commit 0d26ce63 authored by joooeoeee's avatar joooeoeee Committed by GitHub

Update README.md (#11474)

Corrected a typo in the sentence: "`op-geth` embeds upstream geth’s version inside its own version..."
parent d2a9455d
...@@ -104,7 +104,7 @@ Tags of the form `v<semver>`, such as `v1.1.4`, indicate releases of all Go code ...@@ -104,7 +104,7 @@ Tags of the form `v<semver>`, such as `v1.1.4`, indicate releases of all Go code
This naming scheme is required by Golang. This naming scheme is required by Golang.
In the above list, this means these `v<semver` releases contain all `op-*` components and exclude all `contracts-*` components. In the above list, this means these `v<semver` releases contain all `op-*` components and exclude all `contracts-*` components.
`op-geth` embeds upstream geth’s version inside its own version as follows: `vMAJOR.GETH_MAJOR GETH_MINOR GETH_PATCH.PATCH`. `op-geth` embeds upstream geth’s version inside its own version as follows: `vMAJOR.GETH_MAJOR GETH_MINOR GETH_PATCH.PATCH`.
Basically, geth’s version is our minor version. Basically, geth’s version is our minor version.
For example if geth is at `v1.12.0`, the corresponding op-geth version would be `v1.101200.0`. For example if geth is at `v1.12.0`, the corresponding op-geth version would be `v1.101200.0`.
Note that we pad out to three characters for the geth minor version and two characters for the geth patch version. Note that we pad out to three characters for the geth minor version and two characters for the geth patch version.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment