moby--moby/pkg
Phil Estes 8415aeb39a Merge pull request #29366 from unclejack/pkg_return_directly
pkg: return directly without ifs where possible
2016-12-14 21:20:26 +01:00
..
aaparser pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
archive pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
authorization
broadcaster
chrootarchive
devicemapper
directory
discovery
filenotify
fileutils
fsutils pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
gitutils
graphdb
homedir
httputils
idtools pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
integration
ioutils
jsonlog
jsonmessage
listeners
locker
longpath
loopback
mount
namesgenerator
parsers
pidfile pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
platform
plugingetter
plugins
pools
progress
promise
pubsub
random
reexec
registrar
signal
stdcopy
streamformatter
stringid
stringutils
symlink
sysinfo
system
tailfile
tarsum
term
testutil
tlsconfig
truncindex pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
urlutil
useragent
README.md

README.md

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!