Re: changing from syncstate * to a path

2020-02-20 Thread Daniel Lublin
>>Can I move over all the .mbsyncstate and .uidvalidity files to the >>path, adjust the configuration to that, and mbsync would be happy? >> > .mbsyncstate, yes. > *don't* touch .uidvalidity. Ack! >>Where precisely do I place these files in the new `path` to be? >> > that can be derived from the

Re: changing from syncstate * to a path

2020-02-17 Thread Oswald Buddenhagen
On Mon, Feb 17, 2020 at 07:23:30AM -, Daniel Lublin wrote: Can I move over all the .mbsyncstate and .uidvalidity files to the path, adjust the configuration to that, and mbsync would be happy? .mbsyncstate, yes. *don't* touch .uidvalidity. Where precisely do I place these files in the ne

changing from syncstate * to a path

2020-02-16 Thread Daniel Lublin
Hi, I'm trying out a migration from offlineimap to isync. I think I'll be happy with the move! One question; is it feasible to move from a configuration with `SyncState *` to one that uses a separate path, without having re-syncing everything? Can I move over all the .mbsyncstate and .uidvalidit