sapling/hgext/commitcloud
Mark Thomas a55b165063 commitcloud: don't take wlock when storing commit cloud state
Summary: Commit cloud state is stored in the store, so the wlock is not necessary.

Reviewed By: liubov-dmitrieva

Differential Revision: D8121600

fbshipit-source-id: f96f4764e3cf0637cd45a0bc83d1227318ac9083
2018-06-20 12:50:12 -07:00
..
__init__.py commitcloud: don't take wlock when storing commit cloud state 2018-06-20 12:50:12 -07:00
baseservice.py codemod: join the auto-formatter party for commitcloud and intinitepush 2018-05-29 11:20:56 -07:00
commitcloudcommands.py commitcloud add running time for the background cloud sync 2018-06-18 11:08:02 -07:00
commitcloudcommon.py commitcloud fix ux when password is not found in the keychain 2018-06-18 12:49:34 -07:00
commitcloudutil.py commitcloud fix ux when password is not found in the keychain 2018-06-18 12:49:34 -07:00
httpsservice.py commitcloud: bugfix, check was after the option has been used 2018-05-29 14:50:04 -07:00
localservice.py codemod: join the auto-formatter party for commitcloud and intinitepush 2018-05-29 11:20:56 -07:00
service.py codemod: join the auto-formatter party for commitcloud and intinitepush 2018-05-29 11:20:56 -07:00
state.py commitcloud: don't take wlock when storing commit cloud state 2018-06-20 12:50:12 -07:00