etcd-3.1.4/000077500000000000000000000000001306452513700124445ustar00rootroot00000000000000etcd-3.1.4/.dockerignore000066400000000000000000000000051306452513700151130ustar00rootroot00000000000000.git etcd-3.1.4/.github/000077500000000000000000000000001306452513700140045ustar00rootroot00000000000000etcd-3.1.4/.github/ISSUE_TEMPLATE.md000066400000000000000000000004721306452513700165140ustar00rootroot00000000000000# Bug reporting A good bug report has some very specific qualities, so please read over our short document on [reporting bugs][report_bugs] before you submit your bug report. To ask a question, go ahead and ignore this. [report_bugs]: https://github.com/coreos/etcd/blob/master/Documentation/reporting_bugs.md etcd-3.1.4/.github/PULL_REQUEST_TEMPLATE.md000066400000000000000000000003211306452513700176010ustar00rootroot00000000000000# Contributing guidelines Please read our [contribution workflow][contributing] before submitting a pull request. [contributing]: https://github.com/coreos/etcd/blob/master/CONTRIBUTING.md#contribution-flow etcd-3.1.4/.gitignore000066400000000000000000000002611306452513700144330ustar00rootroot00000000000000/coverage /gopath /gopath.proto /go-bindata /machine* /bin .vagrant *.etcd /etcd *.swp /hack/insta-discovery/.env *.test tools/functional-tester/docker/bin hack/tls-setup/certs etcd-3.1.4/.godir000066400000000000000000000000271306452513700135500ustar00rootroot00000000000000github.com/coreos/etcd etcd-3.1.4/.header000066400000000000000000000011211306452513700136700ustar00rootroot00000000000000// Copyright 2016 The etcd Authors // // Licensed under the Apache License, Version 2.0 (the "License"); // you may not use this file except in compliance with the License. // You may obtain a copy of the License at // // http://www.apache.org/licenses/LICENSE-2.0 // // Unless required by applicable law or agreed to in writing, software // distributed under the License is distributed on an "AS IS" BASIS, // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. // See the License for the specific language governing permissions and // limitations under the License. etcd-3.1.4/.travis.yml000066400000000000000000000020701306452513700145540ustar00rootroot00000000000000dist: trusty language: go go_import_path: github.com/coreos/etcd sudo: false go: - 1.7.5 notifications: on_success: never on_failure: never env: matrix: - TARGET=amd64 - TARGET=arm64 - TARGET=arm - TARGET=386 - TARGET=ppc64le matrix: fast_finish: true allow_failures: - go: tip exclude: - go: tip env: TARGET=arm - go: tip env: TARGET=arm64 - go: tip env: TARGET=386 - go: tip env: TARGET=ppc64le addons: apt: packages: - libpcap-dev - libaspell-dev - libhunspell-dev before_install: - go get -v github.com/chzchzchz/goword - go get -v honnef.co/go/simple/cmd/gosimple - go get -v honnef.co/go/unused/cmd/unused # disable godep restore override install: - pushd cmd/etcd && go get -t -v ./... && popd script: - > case "${TARGET}" in amd64) GOARCH=amd64 ./test ;; 386) GOARCH=386 PASSES="build unit" ./test ;; *) # test building out of gopath GO_BUILD_FLAGS="-a -v" GOPATH="" GOARCH="${TARGET}" ./build ;; esac etcd-3.1.4/CONTRIBUTING.md000066400000000000000000000047601306452513700147040ustar00rootroot00000000000000# How to contribute etcd is Apache 2.0 licensed and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers and other resources to make getting your contribution into etcd easier. # Email and chat - Email: [etcd-dev](https://groups.google.com/forum/?hl=en#!forum/etcd-dev) - IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org ## Getting started - Fork the repository on GitHub - Read the README.md for build instructions ## Reporting bugs and creating issues Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](https://github.com/coreos/etcd/blob/master/Documentation/reporting_bugs.md) before you submit your bug report. This document might contain links known issues, another good reason to take a look there, before reporting your bug. ## Contribution flow This is a rough outline of what a contributor's workflow looks like: - Create a topic branch from where you want to base your work. This is usually master. - Make commits of logical units. - Make sure your commit messages are in the proper format (see below). - Push your changes to a topic branch in your fork of the repository. - Submit a pull request to coreos/etcd. - Your PR must receive a LGTM from two maintainers found in the MAINTAINERS file. Thanks for your contributions! ### Code style The coding style suggested by the Golang community is used in etcd. See the [style doc](https://github.com/golang/go/wiki/CodeReviewComments) for details. Please follow this style to make etcd easy to review, maintain and develop. ### Format of the commit message We follow a rough convention for commit messages that is designed to answer two questions: what changed and why. The subject line should feature the what and the body of the commit should describe the why. ``` scripts: add the test-cluster command this uses tmux to setup a test cluster that you can easily kill and start for debugging. Fixes #38 ``` The format can be described more formally as follows: ``` :