bitbake: cooker: Rename confusing 'stop' state to 'forceshutdown'
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 13 Sep 2013 16:31:54 +0000 (17:31 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 14 Sep 2013 07:20:38 +0000 (08:20 +0100)
commit04baae12edeccfa56ab08b25fac2b704a6958d5c
tree62a7193f36f9d24709d075b9a0d266340b8008d8
parentbc41c84efb3a7a6a4fdd2c4917f79e297c9b93f0
bitbake: cooker: Rename confusing 'stop' state to 'forceshutdown'

The shutdown state causes the server to finish what its doing, stop was
them meant to completely stop it. It doesn't mean the server is stopped
though. Renaming the current stop event for forceshutdown gives more
meaning to what it actually does. The stopped namespace then becomes
available to indicate a completely stopped server.

(Bitbake rev: 12e9d33bfae5294e3870dfd1202f63383ad05e92)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/lib/bb/command.py
bitbake/lib/bb/cooker.py
bitbake/lib/bb/server/process.py
bitbake/lib/bb/ui/crumbs/hobeventhandler.py
bitbake/lib/bb/ui/depexp.py
bitbake/lib/bb/ui/goggle.py
bitbake/lib/bb/ui/knotty.py
bitbake/lib/bb/ui/ncurses.py