Improve TestKillDifferentUser to prevent timeout on buildbot
Add GitHub usernames to MAINTAINERS
gitignore all test files
Fix typo in docs for docker run -dns
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.
Merge pull request #1497 from vincentbernat/fix/ipv4-forwarding-detection

runtime: correctly detect IPv4 forwarding
Merge pull request #1499 from seldo/master

* Documentation: Adding a reference to ps -a
Merge pull request #1494 from KSid/typo-docs-run-command

* Documentation: Fix typo in docs for docker run -dns
Merge pull request #1487 from titanous/maintainer-usernames

Add GitHub usernames to MAINTAINERS
Merge pull request #1491 from titanous/gitignore-test

gitignore all test files
Merge pull request #1476 from dotcloud/improve_TestKillDifferentUser

* Tests: Improve TestKillDifferentUser to prevent timeout on buildbot