diff --git a/glide.lock b/glide.lock index 3c8b3bd5..279020c2 100644 --- a/glide.lock +++ b/glide.lock @@ -1,5 +1,5 @@ -hash: e7ed76c4a5812e4c198db9d3f153cac04113225f58bb82966e4eca08386eda20 -updated: 2016-05-12T16:50:32.137050044-07:00 +hash: f3b21a59ce256ab9ea3bb3568d1238397d84993afa2c15fab5b30abb97c558e3 +updated: 2016-06-23T16:06:01.323815777-07:00 imports: - name: github.com/alecthomas/units version: 2efee857e7cfd4f3d0138cc3cbb1b4966962b93a @@ -11,6 +11,10 @@ imports: version: b3f805dee6a4aa5ed298a1f370284df470eecf43 subpackages: - config +- name: github.com/coreos/fuze + version: 60c987a0aba4976ac6cbc9350671c2fedc431e8b + subpackages: + - config - name: github.com/coreos/go-semver version: 294930c1e79c64e7dbe360054274fdad492c8cf5 subpackages: @@ -20,7 +24,7 @@ imports: subpackages: - journal - name: github.com/coreos/ignition - version: 44c274ab414294a8e34b3a940e0ec1afe6b6c610 + version: b6850837b3b9bd17b673e58b5c406b5e4192ddca subpackages: - config - config/types @@ -37,6 +41,8 @@ imports: version: 5215b55f46b2b919f50a1df0eaa5886afe4e3b3d subpackages: - spew +- name: github.com/go-yaml/yaml + version: a83829b6f1293c91addabc89d0571c246397bbf4 - name: github.com/golang/protobuf version: 7cc19b78d562895b13596ddce7aafb59dd789318 subpackages: diff --git a/glide.yaml b/glide.yaml index faeaa367..14a7834f 100644 --- a/glide.yaml +++ b/glide.yaml @@ -18,12 +18,13 @@ import: subpackages: - journal - package: github.com/coreos/ignition - version: 44c274ab414294a8e34b3a940e0ec1afe6b6c610 + version: b6850837b3b9bd17b673e58b5c406b5e4192ddca + subpackages: + - config +- package: github.com/coreos/fuze + version: 60c987a0aba4976ac6cbc9350671c2fedc431e8b subpackages: - config - - config/types - - config/v1 - - config/v1/types - package: github.com/coreos/pkg version: 66fe44ad037ccb80329115cb4db0dbe8e9beb03a subpackages: diff --git a/vendor/github.com/coreos/fuze/.gitignore b/vendor/github.com/coreos/fuze/.gitignore new file mode 100644 index 00000000..53dc7e4a --- /dev/null +++ b/vendor/github.com/coreos/fuze/.gitignore @@ -0,0 +1,3 @@ +bin/ +gopath/ +*.swp diff --git a/vendor/github.com/coreos/fuze/.travis.yml b/vendor/github.com/coreos/fuze/.travis.yml new file mode 100644 index 00000000..9c11341c --- /dev/null +++ b/vendor/github.com/coreos/fuze/.travis.yml @@ -0,0 +1,12 @@ +language: go +matrix: + include: + - go: 1.5 + env: GO15VENDOREXPERIMENT=1 + - go: 1.6 + +install: + - + +script: + - ./test diff --git a/vendor/github.com/coreos/fuze/CONTRIBUTING.md b/vendor/github.com/coreos/fuze/CONTRIBUTING.md new file mode 100644 index 00000000..6662073a --- /dev/null +++ b/vendor/github.com/coreos/fuze/CONTRIBUTING.md @@ -0,0 +1,71 @@ +# How to Contribute + +CoreOS projects are [Apache 2.0 licensed](LICENSE) and accept contributions via +GitHub pull requests. This document outlines some of the conventions on +development workflow, commit message formatting, contact points and other +resources to make it easier to get your contribution accepted. + +# Certificate of Origin + +By contributing to this project you agree to the Developer Certificate of +Origin (DCO). This document was created by the Linux Kernel community and is a +simple statement that you, as a contributor, have the legal right to make the +contribution. See the [DCO](DCO) file for details. + +# Email and Chat + +The project currently uses the general CoreOS email list and IRC channel: +- Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev) +- IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org + +Please avoid emailing maintainers found in the MAINTAINERS file directly. They +are very busy and read the mailing lists. + +## Getting Started + +- Fork the repository on GitHub +- Read the [README](README.md) for build and test instructions +- Play with the project, submit bugs, submit patches! + +## 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 (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. +- Make sure the tests pass, and add any new tests as appropriate. +- Submit a pull request to the original repository. + +Thanks for your contributions! + +### 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: + +``` +: + + + +