Improve TestKillDifferentUser to prevent timeout on buildbot
Fix typo: fmt.Sprint -> fmt.Sprintf
Update AUTHORS
Merge pull request #1481 from titanous/fix-sprint

Fix typo: fmt.Sprint -> fmt.Sprintf
Use ranged for loop on channels
Merge pull request #1484 from titanous/use-range

Use ranged for loop on channels
Add GitHub usernames to MAINTAINERS
Add initial bash completion script

The script can be used to auto-complete commands, image names and
container ids from within a bash prompt.

This partially resolves #336.
Revert "docker.upstart: avoid spawning a `sh` process"

This reverts commit 24dd50490a027f01ea086eb90663d53348fa770e.
Add description and usage information
gitignore all test files
Merge pull request #1489 from dotcloud/1422-revert-upstart

Revert "docker.upstart: avoid spawning a `sh` process"
Missed -entrypoint from 'docker run' options
Clarified bash completion limitations
Still missed -entrypoint from 'docker run'
Fix typo in docs for docker run -dns
Merge pull request #1483 from titanous/update-authors

Update AUTHORS
runtime: correctly detect IPv4 forwarding

When memory cgroup is absent, there was not attempt to detect if IPv4
forwarding was enabled and therefore, docker was printing a warning
for each command spawning a new container. The test for IPv4
forwarding was guarded by the test for memory cgroup.
Adding a reference to ps -a

It was confusing to me as a first-time user that my docker attach command failed; I was expecting the container to run continuously, and when I couldn't attach to it, I assumed something was wrong. ps -a shows that the container still exists, which gives the user confidence to go to the next step.
Install websocket library before building docker