1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
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 Rename Remote API to Engine API 2016-11-22 12:49:38 +00:00
broadcaster
chrootarchive Merge pull request #28047 from cpuguy83/27773_chrootarchive_rbind 2016-11-09 10:52:14 -08:00
devicemapper fix a few golint errors 2016-11-18 18:32:02 -08:00
directory
discovery fix typo 2016-11-18 15:51:36 +08:00
filenotify project: use vndr for vendoring 2016-11-03 15:31:46 -07:00
fileutils Fix use of **/ in .dockerignore 2016-12-02 03:58:54 -08:00
fsutils pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
gitutils
graphdb Windows: Factor out sqlite 2016-12-01 09:38:08 -08:00
homedir
httputils Fix a bit typos 2016-12-09 03:05:11 +08:00
idtools pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
integration Extract daemon to its own package 2016-12-09 22:26:42 +01:00
ioutils s/bCap/bLen/ 2016-11-17 21:05:09 +00:00
jsonlog
jsonmessage pkg/jsonmessage: Avoid undefined ANSI escape codes. 2016-11-10 14:10:47 +00:00
listeners
locker
longpath
loopback
mount Add functional support for Docker sub commands on Solaris 2016-11-07 09:06:34 -08:00
namesgenerator Add some adjectives to the namesgenerator 2016-11-24 18:38:04 +01:00
parsers Fix TestUpdateKernelMemoryUninitialized on new kernel version 2016-08-02 13:17:20 +08:00
pidfile pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
platform Swap usage of LazyDLL and LoadDLL to LazySystemDLL. 2016-11-22 14:57:11 -08:00
plugingetter Refcount graphdriver plugins properly 2016-12-09 19:46:28 -05:00
plugins plugins: container-rootfs-relative paths 2016-12-09 10:16:24 -08:00
pools pkg/pool: no need for double pointer for sync.Pool 2016-10-20 15:27:38 -07:00
progress progress: Rate limit progress bar output 2016-09-14 17:23:16 -07:00
promise
pubsub
random
reexec First header should be a top level header 2016-11-22 09:33:21 +08:00
registrar
signal Move stack dump dir to exec root 2016-11-16 12:55:18 -05:00
stdcopy stdcopy: remove logrus debug messages; makes it easier to vendor without the dependency. 2016-10-26 16:29:37 -07:00
streamformatter
stringid Minor refactor and beter coverage for pkg/stringid 2016-07-20 00:23:06 +02:00
stringutils Implement stringutils.Ellipsis() 2016-08-11 14:14:06 +02:00
symlink Don't attempt to evaluate drive root on Windows 2016-09-08 13:52:54 -07:00
sysinfo Only show global warnings once 2016-11-30 10:11:42 -08:00
system Merge pull request #28683 from darrenstahlmsft/SystemDLL 2016-11-22 16:58:30 -08:00
tailfile Change reading order of tailfile 2016-11-13 20:08:51 -08:00
tarsum fix t.Errorf to t.Error in serveral _test.go 2016-11-14 17:54:43 +08:00
term Windows: Fix crash in docker system prune 2016-12-09 14:23:25 -08:00
testutil Fix broken JSON support in cli/command/formatter 2016-10-17 08:07:17 +00:00
tlsconfig Use system ca pool from tlsconfig 2016-10-31 14:52:07 -07:00
truncindex pkg: return directly without ifs where possible 2016-12-13 22:10:11 +02:00
urlutil
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!