Files
docker-cli/components/engine/pkg
Vivek Goyal eb11479882 devmapper: Use device id as specified by caller
Currently devicemapper CreateDevice and CreateSnapDevice keep on retrying
device creation till a suitable device id is found. 

With new transaction mechanism we need to store device id in transaction
before it has been created.

So change the logic in such a way that caller decides the devices Id to
use. If that device Id is not available, caller bumps up the device Id
and retries.

That way caller can update transaciton too when it tries a new Id. Transaction
related patches will come later in the series.
  
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Upstream-commit: 7b2b15d3e9f9b7ad898a36bbe5ceb42c9ca58d47
Component: engine
2014-12-03 13:06:43 -05:00
..
2014-10-24 15:11:48 -07:00
2014-10-06 22:57:27 +03:00
2014-10-27 18:59:02 +00:00
2014-11-30 01:58:16 +08:00
2014-11-06 11:36:09 -08:00
2014-11-25 18:55:40 -05:00
2014-10-24 15:03:06 -07:00
2014-10-27 18:59:02 +00:00
2014-11-20 19:33:15 +02:00
2014-03-27 22:44:31 +01:00
2014-07-01 23:44:12 +04:00
2014-12-02 15:28:13 -08:00
2014-11-25 20:49:01 +09:00
2014-11-24 18:10:37 -05: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!