You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RUN ETH_DEPS=$(go list -f '{{.Imports}} {{.TestImports}} {{.XTestImports}}' github.com/ethereum/go-ethereum/... | sed -e 's/\[//g' | sed -e 's/\]//g' | sed -e 's/C //g'); if [ "$ETH_DEPS" ]; then go get $ETH_DEPS; fi
*`ethtest` test tool which runs with the [tests](https://github.com/ethereum/testes) suit:
48
+
`ethtest "`cat myfile.json`"`.
49
+
*`evm` is a generic Ethereum Virtual Machine: `evm -code 60ff60ff -gas
50
+
10000 -price 0 -dump`. See `-h` for a detailed description.
51
+
28
52
General command line options
29
-
====================
53
+
============================
30
54
31
55
```
32
-
Shared between ethereum and ethereal
56
+
== Shared between ethereum and Mist ==
57
+
58
+
= Settings
33
59
-id Set the custom identifier of the client (shows up on other clients)
34
60
-port Port on which the server will accept incomming connections
35
61
-upnp Enable UPnP
36
62
-maxpeer Desired amount of peers
37
63
-rpc Start JSON RPC
38
-
39
64
-dir Data directory used to store configs and databases
40
-
-import Import a private key
41
-
-genaddr Generates a new address and private key (destructive action)
42
-
-h This
65
+
66
+
= Utility
67
+
-h This
68
+
-import Import a private key
69
+
-genaddr Generates a new address and private key (destructive action)
70
+
-dump Dump a specific state of a block to stdout given the -number or -hash
71
+
-difftool Supress all output and prints VM output to stdout
72
+
-diff vm=only vm output, all=all output including state storage
43
73
44
74
Ethereum only
45
75
ethereum [options] [filename]
46
76
-js Start the JavaScript REPL
47
77
filename Load the given file and interpret as JavaScript
48
78
-m Start mining blocks
49
79
50
-
Etheral only
80
+
== Mist only ==
81
+
51
82
-asset_path absolute path to GUI assets directory
52
83
```
53
84
54
85
Contribution
55
86
============
56
87
57
-
If you would like to contribute to Ethereum Go, please fork, fix, commit and
58
-
send a pull request to the main repository. Commits which do not comply with the coding standards explained below
59
-
will be ignored. If you send a pull request, make sure that you
60
-
commit to the `develop` branch and that you do not merge to `master`.
61
-
Commits that are directly based off of the `master` branch instead of the `develop` branch will be ignored.
88
+
If you'd like to contribute to Ethereum please fork, fix, commit and
89
+
send a pull request. Commits who do not comply with the coding standards
90
+
are ignored (use gofmt!). If you send pull requests make absolute sure that you
91
+
commit on the `develop` branch and that you do not merge to master.
92
+
Commits that are directly based on master are simply ignored.
62
93
63
-
To make this process simpler try following the [git flow](http://nvie.com/posts/a-successful-git-branching-model/) branching model, as it sets this process up and streamlines work flow.
94
+
To make life easier try [git flow](http://nvie.com/posts/a-successful-git-branching-model/) it sets
95
+
this all up and streamlines your work flow.
64
96
65
97
Coding standards
66
98
================
67
99
68
-
Code should be formatted according to the [Go Formatting
100
+
Sources should be formatted according to the [Go Formatting
Unless struct fields are supposed to be directly accessible, provide
72
-
getters and hide the fields through Go's exporting facility.
103
+
Unless structs fields are supposed to be directly accesible, provide
104
+
Getters and hide the fields through Go's exporting facility.
73
105
74
-
Make comments in your code meaningful and only use them when necessary. Describe in detail what your code is trying to achieve. For example, this would be redundant and unnecessary commenting:
106
+
When you comment put meaningfull comments. Describe in detail what you
107
+
want to achieve.
75
108
76
109
*wrong*
77
110
@@ -82,7 +115,12 @@ if x > y {
82
115
}
83
116
```
84
117
85
-
Everyone reading the source code should know what this code snippet was meant to achieve, and so those are **not** meaningful comments.
118
+
Everyone reading the source probably know what you wanted to achieve
119
+
with above code. Those are **not** meaningful comments.
86
120
87
-
While this project is constantly tested and run, code tests should be written regardless. There is not time to evaluate every person's code specifically, so it is expected of you to write tests for the code so that it does not have to be tested manually. In fact, contributing by simply writing tests is perfectly fine!
121
+
While the project isn't 100% tested I want you to write tests non the
122
+
less. I haven't got time to evaluate everyone's code in detail so I
123
+
expect you to write tests for me so I don't have to test your code
124
+
manually. (If you want to contribute by just writing tests that's fine
0 commit comments