pax_global_header00006660000000000000000000000064131600552760014517gustar00rootroot0000000000000052 comment=a389bdde4dd695d414e47b755e95e72b7826432c dbus-4.1.0/000077500000000000000000000000001316005527600124565ustar00rootroot00000000000000dbus-4.1.0/.travis.yml000066400000000000000000000007671316005527600146010ustar00rootroot00000000000000dist: precise language: go go_import_path: github.com/godbus/dbus sudo: true go: - 1.6.3 - 1.7.3 - tip env: global: 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: - dbus - dbus-x11 before_install: dbus-4.1.0/CONTRIBUTING.md000066400000000000000000000027141316005527600147130ustar00rootroot00000000000000# 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: ``` :