muchsync files renames

[Amadeusz Żołnowski]

David Mazieres <dm-list-email-notmuch at scs.stanford.edu> writes:
> Initially, when you run "muchsync --init", it copies all the files to
> your maildir, and for each file invokes
> notmuch_message_tags_to_maildir_flag.  That changes the name of the
> file, with the result that the sql database and the actual mail
> directory end up out of sync.  That on it's own is not a big deal, but
> it means that the next time muchsync, muchsync will have to rescan all
> of the files, as their names are no longer correct.  That shouldn't
> cause any extra traffic between the two machines, but it will require
> time on the client.  That is likely the source of the delay you were
> seeing.

Yes, that seems to be probable scenario.

> However, if you C-c the client during this process, I still don't see
> any problems arising that cause more links to be transferred between
> machines.  So I'm kind of stumped about that part.

I don't think that C-c caused more links transfers. It's just about that
on rerun (after C-c) the notmuch on server reported renames which
probably took place in the previous run.

-- 
Amadeusz Żołnowski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 950 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20150824/0e239c83/attachment.sig>