forked from ethereum/go-ethereum
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ugly README #1
Comments
Nobody manage this repo? Passed 5 days. |
Wow 10 days have passed. Amazing repo. It seems like a scam. |
15 days... There is no doubt that it is scam. @sadoci don’t have any responsibility. |
Thanks for picking up typos. Fixed issues raised here, except |
cp-wjhan
pushed a commit
to cp-wjhan/go-metadium
that referenced
this issue
Jul 31, 2023
fix compile error due to unsupported function UnixMilli()
cp-wjhan
pushed a commit
to cp-wjhan/go-metadium
that referenced
this issue
Jul 31, 2023
cp-wjhan
pushed a commit
to cp-wjhan/go-metadium
that referenced
this issue
Jul 31, 2023
update the error handling routine by Sooho's QA result (Low METADIUM#1).
cp-wjhan
pushed a commit
to cp-wjhan/go-metadium
that referenced
this issue
Jul 31, 2023
Feat : getReceipts() API 추가
cp-wjhan
pushed a commit
to cp-wjhan/go-metadium
that referenced
this issue
Aug 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
README is ugly, even it was just forked.
Why don't you keep consistency for wording?
Because of this, I am confused to start
Expected behaviour
In README.md, all wording about console should be
gmet
orgmeta
or somethingActual behaviour
In README.md,
gmet
,gmeth
,geth
are mixedSteps to reproduce the behaviour
Open README
The text was updated successfully, but these errors were encountered: