Hello, On 2025-02-21 12:49, Lars Kotthoff <li...@larsko.org> writes:
> Hmmm, as far as I can tell the reason that only one machine should sync is > that > the file names for the mail files are not preserved by muchsync. This causes > issues with mbsync as it uses the filename to store the UID. I’m afraid mbsync also has some internal state that stores what has been synchronized (in ~/.mbsync in my case). Maybe it would work fine when preserving the file name (i.e., mbsync would think it needs to fetch a file and then see that it is already available), but I have not tried. I’m also considering synchronizing my mail files using another mechanism (unison), as I already use it for a lot of stuff. Being able to separately propagate the state of notmuch would be really useful in that case. Reading the page of notmuch-git, it seems that it is exactly what it is meant for. But I’m not sure it is actually used this way. Best, Alan
signature.asc
Description: PGP signature
_______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
