-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
chore(deps:go-multiaddr) update to b90678896b52c #46
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
chore(deps:go-multiaddr) update to b90678896b52c #46
Conversation
procedure is to execute ``` cd my/github.com/jbenet/go-multiaddr git pull cd my/github.com/jbenet/go-ipfs godep update github.com/jbenet/go-multiaddr ```
65f55ad
to
7f39299
Compare
So, youre following some sort of standard for your naming conventions of branches, issues, and pull requests. Is there some sort of spec i can read through? I kinda like it. |
The style you're seeing is an amalgamation of git flow and the angular js conventions. No hard and fast rules. Angular JS commit message conventions (PR/issue names, commit messages): Git Flow (branch naming): Design Goals:
|
Awesome, thanks @perfmode |
…a4c8176805c6facc3fe3eb82 chore(deps:go-multiaddr) update to b90678896b52c
add env vars for logging to file and syslog
plugins: don't omit empty config values
plugins: don't omit empty config values
plugins: don't omit empty config values
plugins: don't omit empty config values
No description provided.