git backend: actually update local cache from remote

Dirk Hohndel dirk at hohndel.org
Thu Jun 11 06:28:02 PDT 2015


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"?
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.

/D


More information about the subsurface mailing list