From 689e8ec9493a4294856dc1568f5ef667e106707c Mon Sep 17 00:00:00 2001 From: Alexander Morozov Date: Thu, 29 Jan 2015 15:35:22 -0800 Subject: [PATCH] Update github.com/godbus/dbus to v2 Signed-off-by: Alexander Morozov --- update-vendor.sh | 2 +- .../github.com/godbus/dbus/CONTRIBUTING.md | 50 ++++++++++ vendor/src/github.com/godbus/dbus/MAINTAINERS | 2 + vendor/src/github.com/godbus/dbus/conn.go | 26 +++-- .../godbus/dbus/introspect/introspect.go | 6 ++ .../godbus/dbus/introspect/introspectable.go | 5 +- .../src/github.com/godbus/dbus/prop/prop.go | 8 +- .../github.com/godbus/dbus/transport_unix.go | 6 ++ .../dbus/transport_unixcred_dragonfly.go | 95 +++++++++++++++++++ ...nixcred.go => transport_unixcred_linux.go} | 5 +- vendor/src/github.com/godbus/dbus/variant.go | 14 ++- 11 files changed, 200 insertions(+), 19 deletions(-) create mode 100644 vendor/src/github.com/godbus/dbus/CONTRIBUTING.md create mode 100644 vendor/src/github.com/godbus/dbus/MAINTAINERS create mode 100644 vendor/src/github.com/godbus/dbus/transport_unixcred_dragonfly.go rename vendor/src/github.com/godbus/dbus/{transport_unixcred.go => transport_unixcred_linux.go} (61%) diff --git a/update-vendor.sh b/update-vendor.sh index df66a0a8d..15bae1858 100755 --- a/update-vendor.sh +++ b/update-vendor.sh @@ -42,7 +42,7 @@ clone() { # the following lines are in sorted order, FYI clone git github.com/codegangsta/cli 1.1.0 clone git github.com/coreos/go-systemd v2 -clone git github.com/godbus/dbus v1 +clone git github.com/godbus/dbus v2 clone git github.com/syndtr/gocapability 3c85049eae # intentionally not vendoring Docker itself... that'd be a circle :) diff --git a/vendor/src/github.com/godbus/dbus/CONTRIBUTING.md b/vendor/src/github.com/godbus/dbus/CONTRIBUTING.md new file mode 100644 index 000000000..c88f9b2bd --- /dev/null +++ b/vendor/src/github.com/godbus/dbus/CONTRIBUTING.md @@ -0,0 +1,50 @@ +# How to Contribute + +## Getting Started + +- Fork the repository on GitHub +- Read the [README](README.markdown) 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: + +``` +: + + + +