[Buildbot-commits] [Buildbot] #2160: Interlock documentation refers to "shared" lock mode, should be "exclusive"

[Buildbot]

#2160: Interlock documentation refers to "shared" lock mode, should be "exclusive"
--------------------+------------------------
Reporter:  ggolan   |       Owner:
    Type:  defect   |      Status:  closed
Priority:  trivial  |   Milestone:  undecided
 Version:  0.8.5    |  Resolution:  duplicate
Keywords:  docs     |
--------------------+------------------------
Changes (by dustin):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 This was fixed already, and is visible in the "latest" docs on
 buildbot.net.

 {{{
 commit ee7d36d5609d19b3f9372e134306572055e9f9c4
 Author: William Deegan <bill at baddogconsulting.com>
 Date:   Tue Sep 20 14:13:29 2011 -0700

     fixed lock mode description, should be counting or exclusive and not
 counting or shared

 diff --git a/master/docs/manual/cfg-interlocks.rst b/master/docs/manual
 /cfg-interlocks.rst
 index f1399f8..3265979 100644
 --- a/master/docs/manual/cfg-interlocks.rst
 +++ b/master/docs/manual/cfg-interlocks.rst
 @@ -87,7 +87,7 @@ locks at other times.
  To use locks, you add them with a ``locks`` argument to a build or a
 step.
  Each use of a lock is either in counting mode (that is, possibly shared
 with
  other builds) or in exclusive mode, and this is indicated with the syntax
 -``lock.access(mode)``, where :data:`mode` is one of ``"counting"`` or
 ``"shared"``.
 +``lock.access(mode)``, where :data:`mode` is one of ``"counting"`` or
 ``"exclusive"``.

  A build or build step proceeds only when it has acquired all locks. If a
 build
  or step needs a lot of locks, it may be starved [#]_ by other builds that
 need
 }}}

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2160#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation