Files
docker-cli/components/engine/pkg
Kristina Zabunova 208ac7a049 Increased test coverage of httputils to 70 %
Signed-off-by: Kristina Zabunova <triara.xiii@gmail.com>
(cherry picked from commit d71817464e859cd323d6cdaf4dec5a9dd530f57e)
Upstream-commit: b3f999e86331b3c19572a88b5e123ea961ac54fb
Component: engine
2015-08-28 10:41:19 -04:00
..
2015-07-29 21:25:56 +03:00
2015-07-16 16:02:26 -07:00
2015-06-17 01:16:57 +03:00
2015-07-22 10:26:10 +02:00
2015-07-27 21:26:21 +02:00
2015-08-26 13:37:52 -04:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-29 21:25:56 +03:00
2015-07-27 21:26:21 +02:00
2015-07-29 21:25:56 +03:00
2015-07-27 21:26:21 +02:00
2015-08-26 12:38:28 -07:00
2015-08-25 16:50:08 -04:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-03-25 00:46:22 +08: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!