git backend: actually update local cache from remote

[Martin Gysel]

Am 11.06.2015 um 15:28 schrieb Dirk Hohndel:
> On Thu, Jun 11, 2015 at 12:15:12PM +0200, Martin Gysel wrote:
>>>
>>> I would to all cloud access in the background and offer the user (via
>>> a modal dialog) to reload when the background operation finished and
>>> implied an update to the currently displayed log.
>>>
>>> I never thought these operations are that hard to design a good
>>> workflow/UI for. I thought, only conflict resolution and version
>>> management beyond opening a terminal and ask the user to fix it on
>>> the command line would be hard…
>>
>> please don't do any cloud sync in the background unconditionally. either
>> have something like a 'automatically sync with cloud' setting or allow
>> the user to trigger or at least cancel the sync.
> 
> Yes, I'd have an option in the preferences. Would you object to this
> option defaulting to "on"?

that's ok...

> How would a "cancel" of a background sync work? How would I trigger that?
> 
> I'm just trying to understand what you have in mind.

like you described earlier, using the spinner or a similar dialog which
is visible when synching