James Bardin 3f0dcd1308 Have the clistate Lock use LockWithContext ... - Have the ui Lock helper use state.LockWithContext. - Rename the message package to clistate, since that's how it's imported everywhere. - Use a more idiomatic placement of the Context in the LockWithContext args.		2017-04-01 17:09:20 -04:00
..
remote	convert S3 remote state to a backend	2017-03-22 10:59:37 -04:00
testdata	Use NewLockInfo to get a pre-populated value	2017-02-15 14:41:55 -05:00
backup.go	remove extra state.Locker assertions	2017-04-01 17:01:45 -04:00
backup_test.go	state/remote: export ClientLocker, test for implementation	2017-02-15 14:20:59 -08:00
inmem.go	All states are lockers	2017-04-01 17:01:12 -04:00
inmem_test.go	state: InmemState	2015-02-23 15:13:55 -08:00
local.go	fix windows locking	2017-02-17 13:29:48 -05:00
local_lock_unix.go	Switch from Path to PathOut on LocalState.written	2017-01-30 17:16:57 -05:00
local_lock_windows.go	fix windows locking	2017-02-17 13:29:48 -05:00
local_test.go	test failure for windows local locks	2017-02-17 13:29:47 -05:00
lock.go	backend/consul: support "lock" option to disable locking	2017-03-14 17:59:10 -07:00
lock_test.go	backend/consul: support "lock" option to disable locking	2017-03-14 17:59:10 -07:00
state.go	Have the clistate Lock use LockWithContext	2017-04-01 17:09:20 -04:00
state_test.go	Clean up LockInfo and LockError and use them	2017-02-15 14:44:43 -05:00
testing.go	Fix vet issues	2016-10-18 11:11:12 -04:00