cri-o/vendor/github.com/docker/docker/pkg
Antonio Murdaca d6e819133d
*: initial update to kube 1.8
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
2017-11-02 16:07:51 +01:00
..
homedir Add docker/config package to containers/image/pkg 2017-10-10 16:58:40 -04:00
idtools Add docker/config package to containers/image/pkg 2017-10-10 16:58:40 -04:00
ioutils Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
longpath vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
mount Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
pools Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
signal Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
stringid Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
stringutils Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
symlink Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
system Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
templates *: initial update to kube 1.8 2017-11-02 16:07:51 +01:00
term Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
tlsconfig Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
truncindex Move to new github.com/sirupsen/logrus. 2017-08-07 11:50:04 -04:00
README.md Switch to github.com/golang/dep for vendoring 2017-01-31 16:45:59 -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!