moby--moby/pkg
Sebastiaan van Stijn 13ea237234
devicemapper: remove unused errors
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-08-07 12:27:44 +02:00
..
aaparser
archive
authorization
broadcaster
capabilities
chrootarchive Initialize nss libraries in Glibc so that the dynamic libraries are loaded in the host 2019-07-26 01:27:57 +00:00
containerfs
devicemapper devicemapper: remove unused errors 2019-08-07 12:27:44 +02:00
directory
discovery
dmesg
filenotify
fileutils
fsutils
homedir
idtools
ioutils Fixed the inconsistence and also a potential data race in pkg/ioutils/bytespipe.go: bp.closeErr is read/write 8 times; 7 out of 8 times it is protected by bp.mu.Lock(); 1 out of 8 times it is read without a Lock 2019-07-01 11:38:38 -07:00
jsonmessage
locker
longpath
loopback cast Dev and Rdev of Stat_t to uint64 for mips 2019-08-01 20:22:49 +08:00
mount
namesgenerator Remove cocky from names-generator 2019-07-02 16:51:11 +00:00
parsers Enhance container detection on some corner cases. 2019-07-08 15:31:41 -04:00
pidfile
platform
plugingetter
plugins Merge pull request #39422 from lemrouch/35876-workaround 2019-07-22 10:21:50 -07:00
pools
progress
pubsub
reexec
signal
stdcopy
streamformatter
stringid
symlink
sysinfo
system cast Dev and Rdev of Stat_t to uint64 for mips 2019-08-01 20:22:49 +08:00
tailfile
tarsum
term
truncindex
urlutil
useragent
README.md

README.md

pkg/ is a collection of utility packages used by the Moby project without being specific to its internals.

Utility packages are kept separate from the moby 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 Moby 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!