On 09.10.2012 12:42:04, Patrick Ohly wrote:
On Tue, 2012-10-09 at 10:52 +0600, Ildar Mulyukov wrote:
> On 08.10.2012 17:19:17, Patrick Ohly wrote:
> > On Mon, 2012-10-08 at 16:41 +0600, Ildar Mulyukov wrote:
> > $ syncevolution sync=?
> [...]
> > refresh/one-way-from-server/client are also supported. Their
use is
> > discouraged because the direction of the data transfer depends
> > on the role of the local side (can be server or client), which
is
> > not always obvious.
>
> em.. but sync-ui produces exactly sync=one-way-from-server . A bug?
The sync-ui cannot configure local sync. Did you set up the local sync
manually and then change it in the sync-ui?
Surely not.
The commands that I used were quoted in the 1st letter.
What I mean is that *by docs* one-way-from-server is discouraged, but
*sync-ui* produces exactly sync=one-way-from-server if you turn off
"Send changes to Google". That sounds odd.
This is similar to configuring a phone for direct syncing, which also
has the "peerIsClient" flag set. The UI should be able to reverse the
data flow direction in this case, but I have never tested it for local
syncs.
Not the case.
I'm lucky Google has a tiny time-machine behind the "Restore
contacts" command.
> >
> > SyncEvolution also has a builtin backup mechanism that you could
have
> > used. "I feel lucky" also works outside of Google.
>
> I still can't find a note how to _restore_ from this backup.
From the UI:
https://syncevolution.org/documentation/synchronization-guis
[...]
From the command line:
https://syncevolution.org/documentation/syncevolution-usage
Please forgive my dumbiness.
Regards,
--
Ildar
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
