Files
docker-cli/components/engine/pkg
Tobias Klauser 4437cd08db sysinfo: use Prctl() from x/sys/unix
Use unix.Prctl() instead of manually reimplementing it using
unix.RawSyscall. Also use unix.SECCOMP_MODE_FILTER instead of locally
defining it.

Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Upstream-commit: 6c9d715a8c64a7c782b8c7b57925e1dc19b29517
Component: engine
2017-07-17 10:37:42 +02:00
..
2017-07-03 13:13:09 -07:00
2016-12-27 17:32:15 +08:00
2017-07-03 13:13:09 -07:00
2017-04-21 12:31:16 -04:00
2017-06-01 16:22:00 -07:00
2017-07-03 10:32:47 -07:00
2017-04-27 09:26:21 -07:00
2016-12-28 09:43:27 +08:00
2017-05-08 17:02:02 -07:00
2017-07-03 13:13:09 -07:00
2017-07-03 13:13:09 -07:00
2017-07-03 13:13:09 -07:00
2017-05-08 17:02:02 -07:00
2017-05-08 17:02:02 -07:00
2016-11-13 20:08:51 -08:00
2017-07-03 13:13:09 -07:00
2017-07-03 13:13:09 -07:00
2017-06-19 15:59:00 +03:00
2017-06-26 10:07:04 -07:00

pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.

Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.

The directory pkg is named after the same directory in the camlistore project. Since Brad is a core Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!

Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!