cri-o/vendor/github.com/docker/docker/pkg
Antonio Murdaca b211061016
copy using bytes pools
Vendor and use docker/pkg/pools.
pools are used to lower the number of memory allocations and reuse buffers when
processing large streams operations..

The use of pools.Copy avoids io.Copy's internal buffer allocation.
This commit replaces io.Copy with pools.Copy to avoid the allocation of
buffers in io.Copy.

Signed-off-by: Antonio Murdaca <runcom@redhat.com>
2017-06-12 12:53:23 +02:00
..
ioutils vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
longpath vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
mount vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
pools copy using bytes pools 2017-06-12 12:53:23 +02:00
random vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
registrar vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
signal Switch to github.com/golang/dep for vendoring 2017-01-31 16:45:59 -08:00
stringid vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
stringutils vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
symlink vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
system vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
term vendor: remove dep and use vndr 2017-06-07 00:04:21 +02:00
tlsconfig Switch to github.com/golang/dep for vendoring 2017-01-31 16:45:59 -08:00
truncindex vendor: remove dep and use vndr 2017-06-07 00:04:21 +02: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!