Files
docker-cli/components/engine/pkg
Kir Kolyshkin 59f36f3793 devmapper_wrapper.go: fix gcc warning
I am getting the following warning from gcc when compiling the daemon:

> # github.com/docker/docker/pkg/devicemapper
> pkg/devicemapper/devmapper_wrapper.go: In function ‘log_cb’:
> pkg/devicemapper/devmapper_wrapper.go:20:2: warning: ignoring return
> value of ‘vasprintf’, declared with attribute warn_unused_result
> [-Wunused-result]
>  vasprintf(&buffer, f, ap);
>  ^

vasprintf(3) man page says if the function returns -1, the buffer is
undefined, so we should not use it. In practice, I assume, this never
happens so we just return.

Introduced by https://github.com/moby/moby/pull/33845 that resulted in
commit 63328c6 ("devicemapper: remove 256 character limit of libdm logs")

Cc: Aleksa Sarai <asarai@suse.de>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Upstream-commit: 7da12bcfa9db4d84b2c547bee93dafeaead15b16
Component: engine
2017-07-17 17:46:44 -07:00
..
2017-07-03 13:13:09 -07:00
2016-12-27 17:32:15 +08:00
2017-07-03 13:13:09 -07:00
2017-04-21 12:31:16 -04:00
2017-06-01 16:22:00 -07:00
2017-07-03 10:32:47 -07:00
2017-04-27 09:26:21 -07:00
2016-12-28 09:43:27 +08:00
2017-05-08 17:02:02 -07:00
2017-07-03 13:13:09 -07:00
2017-07-03 13:13:09 -07:00
2017-05-08 17:02:02 -07:00
2017-05-08 17:02:02 -07:00
2016-11-13 20:08:51 -08:00
2017-07-03 13:13:09 -07:00
2017-07-03 13:13:09 -07:00
2017-06-19 15:59:00 +03:00
2017-06-26 10:07:04 -07: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!