Closed splasky closed 4 years ago
The changes did not reflect the subject of this pull request.
Don't mix copyright date change and return type tweaks in single pull request.
You have to explain why and how you would like to perform these changes within both pull request and commit messages.
@jserv This PR was originally open by me. I aimed to use a unique error return code throughout TA-endpoint
@jserv This PR was originally open by me. I aimed to use a unique error return code throughout TA-endpoint
Make the task great again. Improve the descriptions in both issue tracker and pull request.
@jserv This PR was originally open by me. I aimed to use a unique error return code throughout TA-endpoint
Make the task great again. Improve the descriptions in both issue tracker and pull request.
I will open a issue tracker for these.
Use git rebase -i
to rework commit messages. Less commits and more expressions.
Always say, "Tangle-accelerator." Be aware of the formal term.
There were some grammar errors in git commit messages. Use shell checkers to validate.
"Fix memory leak" should take place in another pull request.
Issue #37 explained the motivation and considerations for this change, and the commit message of this pull request and git should extend it as well.
The message
Renmae
http_retcode_t
toretcode_t
for general error coverage. lacks of informative reasons.
These commits fixed the following things: Renmae
http_retcode_t
toretcode_t
for general error and status coverage. Add new status code insideutils/defined_error.h
if you needed.closes #37