keycard-go/vendor/github.com/ethereum/go-ethereum/_assets/patches
Andrea Franz d92ae609b7
use status go-ethereum
2018-11-14 09:45:12 +01:00
..
0000-accounts-hd-keys.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0014-whisperv6-notifications.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0016-fix-leveldb-issue.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0021-backends-simulated-chain-signer.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0022-node-attach-public.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0023-extract-personal-sign-api.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0025-whisper-confirmations.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0027-whisper-time-source.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0028-p2p-watchdog.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0029-node-api-gauge-metric.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0032-send-mailserver-request-completed-code.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0033-mailserver-response-contains-cursor.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0035-add_goroutines_metrics.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0037-whisper-metrics.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
0039-enable-metrics-during-compilation.patch use status go-ethereum 2018-11-14 09:45:12 +01:00
README.md use status go-ethereum 2018-11-14 09:45:12 +01:00
patcher use status go-ethereum 2018-11-14 09:45:12 +01:00

README.md

Status Patches for geth (go-ethereum)

status-go uses go-ethereum as its dependency. As any other Go dependency go-ethereum code is vendored and stored in vendor/ folder.

However, there are a few changes has been made to the upstream, that are specific to Status and should not be merged to the upstream. We keep those changes as a set of patches, that can be applied upon each next release of go-ethereum. Patched version of go-ethereum is available in vendor folder.

We try to minimize number and amount of changes in those patches as much as possible, and whereas possible, to contribute changes into the upstream.

Creating patches

Instructions for creating a patch from the command line:

  1. Do changes in vendor/github.com/ethereum/go-ethereum/,
  2. Go to the root status-go directory,
  3. Create a patch git diff --relative=vendor/github.com/ethereum/go-ethereum > _assets/patches/geth/0000-name-of-the-patch.patch
  4. Commit changes.

Updating patches

  1. Tweak the patch file.
  2. Run make dep-ensure to re-apply patches.

Removing patches

  1. Remove the patch file
  2. Remove the link from [this README] (./README.md)
  3. Run make dep-ensure to re-apply patches.

Updating

When a new stable release of go-ethereum comes out, we need to upgrade our vendored copy. We use dep for vendoring, so for upgrading:

  • Change target branch for go-ethereum in Gopkg.toml.
  • dep ensure -update github.com/ethereum/go-ethereum
  • make dep-ensure

This will ensure that dependency is upgraded and fully patched. Upon success, you can do make vendor-check after committing all the changes, in order to ensure that all changes are valid.