Files
docker-cli/components/engine/pkg
Vincent Batts 8b5a2050f9 loopback: separate loop logic from devicemapper
The loopback logic is not technically exclusive to the devicemapper
driver. This reorganizes the code such that the loopback code is usable
outside of the devicemapper package and driver.

Signed-off-by: Vincent Batts <vbatts@redhat.com>
Upstream-commit: af597527121c0ad973e9d0ae4f9cf970da1513cc
Component: engine
2015-12-18 10:57:43 -05:00
..
2015-12-13 18:04:12 +02:00
2015-07-16 16:02:26 -07:00
2015-09-09 14:59:25 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-07-27 21:26:21 +02:00
2015-12-17 11:05:50 +01:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-12-02 16:43:49 -05:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-12-13 18:04:12 +02:00
2015-11-02 08:02:25 -08:00
2015-07-27 21:26:21 +02:00
2015-07-27 21:26:21 +02:00
2015-12-17 11:52:23 +01:00
2013-12-23 23:12:19 +00: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!