1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
moby--moby/pkg
Brian Goff e8c2a33b74 Merge pull request #33139 from stevvooe/remove-unused-functions
pkg/ioutils: remove unused functions
2017-05-10 16:48:14 -04:00
..
aaparser pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
archive Remove pkg/testutil/assert in favor of testify 2017-04-14 12:03:21 -07:00
authorization When authz plugin is disabled, remove from authz middleware chain. 2017-03-22 12:07:39 -07:00
broadcaster
chrootarchive pkg/{chroot,}archive: clean up a few small issues 2017-03-30 16:37:54 +03:00
devicemapper Make pkg/devicemapper and pkg/loopback depend on cgo in build tags 2017-03-29 17:55:42 -07:00
directory
discovery Update docker daemon to dockerd 2016-12-27 17:32:15 +08:00
filenotify pkg/file{utils,notify}: don't compare to bool 2017-03-30 16:38:01 +03:00
fileutils Enable a unit test on windows. 2017-04-21 12:31:16 -04:00
fsutils pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
gitutils
homedir gcplogs: forcibly set HOME on static UNIX binary 2016-12-29 03:17:26 +00:00
httputils Fix escaped go vet error 2017-01-18 00:13:09 +08:00
idtools pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
ioutils pkg/ioutils: remove unused functions 2017-05-10 08:34:16 -07:00
jsonlog pkg/*: clean up a few issues 2017-03-30 16:50:46 +03:00
jsonmessage Add docker build --iidfile=FILE 2017-05-05 16:35:54 +01:00
listeners Don't error with empty group 2017-04-27 09:26:21 -07:00
locker fix some typos 2016-12-28 09:43:27 +08:00
longpath
loopback Make pkg/devicemapper and pkg/loopback depend on cgo in build tags 2017-03-29 17:55:42 -07:00
mount Do not remove containers from memory on error 2017-05-05 17:02:04 -04:00
namesgenerator Add Johannes Kepler and Mary Jackson to name generator 2017-03-17 20:36:12 -07:00
parsers Fix building client on OpenBSD 2017-03-26 20:47:18 +00:00
pidfile pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
platform
plugingetter plugingetter: Avoid all caps for constant declarations 2017-01-04 10:19:04 -08:00
plugins Merge pull request #32222 from unclejack/small_cleanup 2017-03-30 21:09:39 +02:00
pools
progress Synchronous service create and service update 2017-04-03 09:46:01 -07:00
promise
pubsub
random Fix typos found across repository 2015-12-13 18:04:12 +02:00
reexec
registrar pkg/*: clean up a few issues 2017-03-30 16:50:46 +03:00
signal
stdcopy fix docker logs error handling 2017-02-14 14:38:42 -08:00
streamformatter Add docker build --iidfile=FILE 2017-05-05 16:35:54 +01:00
stringid Move imageID validation to stringid pkg 2016-12-26 18:53:22 -08:00
stringutils change minor mistake of spelling 2016-12-20 21:05:19 +08:00
symlink Update copyright dates 2017-02-24 19:41:59 +00:00
sysinfo
system Do not remove containers from memory on error 2017-05-05 17:02:04 -04:00
tailfile
tarsum Add support for COPY from previous rootfs 2017-03-23 15:12:15 -07:00
templates Disable HTML escaping for JSON in formatter 2017-05-09 10:16:10 +03:00
term Add OPOST back to !cgo build for pkg/term 2017-05-09 16:36:17 -07:00
testutil Use cli for trusted relate command 2017-04-19 14:04:39 +02:00
tlsconfig
truncindex Fix non thread-safe Iteration around go-patricia 2017-01-09 17:06:50 +00:00
urlutil pkg/urlutil: don't compare to bool 2017-03-30 16:38:01 +03:00
useragent
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!