Files
docker-cli/components/engine/pkg
Sam Abed 2b816e64e2 Show pull progress in terminal for inflight pull requests
Based on #12874 from Sam Abed <sam.abed@gmail.com>. His original commit
was brought up to date by manually porting the changes in pull.go into
the new code in pull_v1.go and pull_v2.go.

Fixes #8385

Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
Upstream-commit: 572f008e892b06262963ccb75c631f2f5d6c6fcd
Component: engine
2015-08-27 11:18:40 -07:00
..
2015-07-29 21:25:56 +03:00
2015-07-16 16:02:26 -07:00
2015-08-03 09:45:05 +08: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!