Skip to content
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.

Fix golint warnings #157

Merged
merged 1 commit into from
Nov 2, 2016
Merged

Fix golint warnings #157

merged 1 commit into from
Nov 2, 2016

Conversation

prashanthpai
Copy link
Contributor

Barring transaction subpackage which contains mainly generated code,
other subpackages have had their golint warnings fixed.

We would want to ensure that all new code adheres to golint.

Signed-off-by: Prashanth Pai ppai@redhat.com

@purpleidea
Copy link

We would want to ensure that all new code adheres to golint.

You probably want to make sure that all code adheres to go vet. Golint is usually right, but not always!

@kshlm
Copy link
Member

kshlm commented Oct 28, 2016

@purpleidea, we're using gometalinter, which runs a bunch of stuff, including golint and go vet.

2 similar comments
@kshlm
Copy link
Member

kshlm commented Oct 28, 2016

@purpleidea, we're using gometalinter, which runs a bunch of stuff, including golint and go vet.

@kshlm
Copy link
Member

kshlm commented Oct 28, 2016

@purpleidea, we're using gometalinter, which runs a bunch of stuff, including golint and go vet.

Barring transaction subpackage which contains mainly generated code,
other subpackages have had their golint warnings fixed.

We would want to ensure that all new code adheres to golint.

Signed-off-by: Prashanth Pai <ppai@redhat.com>
@prashanthpai
Copy link
Contributor Author

@kshlm Rebased to master. Consider merging this.

@kshlm kshlm merged commit d96f3bf into gluster:master Nov 2, 2016
@kshlm kshlm removed the in progress label Nov 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants