Files
docker-cli/components/engine/pkg
Vivek Goyal 75da15eccc devmapper: Call UdevWait() even in failure path
Currently we set up a cookie and upon failure not call UdevWait(). This
does not cleanup the cookie and associated semaphore and system will
soon max out on total number of semaphores.

To avoid this, call UdevWait() even in failure path which in turn will
cleanup associated semaphore.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Vincent Batts <vbatts@redhat.com>
Upstream-commit: edc6df256d21eb1d1aa36b241dcc6d4b83d58d75
Component: engine
2014-11-15 09:41:27 -05:00
..
2014-11-11 18:01:08 -05:00
2014-10-24 15:11:48 -07:00
2014-10-06 22:57:27 +03:00
2014-11-03 23:09:08 -05:00
2014-10-27 18:59:02 +00:00
2014-08-29 15:38:03 +10:00
2014-11-06 11:36:09 -08:00
2014-10-24 15:03:06 -07:00
2014-10-24 15:03:06 -07:00
2014-10-26 13:55:29 +08:00
2014-10-27 18:59:02 +00:00
2014-10-22 14:05:45 -07:00
2014-03-27 22:44:31 +01:00
2014-07-01 23:44:12 +04:00
2013-12-23 23:12:19 +00: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!