From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: David Bremner <david@tethera.net>,
David Mazieres expires 2015-11-29 PST
<mazieres-sggp47c7j46624db3rharctcei@temporary-address.scs.stanford.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: muchsync files renames
Date: Wed, 09 Sep 2015 18:49:28 +0100 [thread overview]
Message-ID: <877fnzmqjb.fsf@freja.aidecoe.name> (raw)
In-Reply-To: <87r3mge81s.fsf@maritornes.cs.unb.ca>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
Thank you David B. for explanation. I think that everything is clear
now.
David M., what about updating your website on that? I think it's
important to warn about possible files moves between new/ and cur/.
And what I can do is to prepare patches for afew to handle it
appropriately.
--
Amadeusz Żołnowski
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 950 bytes --]
prev parent reply other threads:[~2015-09-09 17:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 21:02 muchsync files renames Amadeusz Żołnowski
2015-08-23 5:41 ` David Mazieres
2015-08-23 8:44 ` Amadeusz Żołnowski
2015-08-23 20:06 ` David Mazieres
2015-08-23 20:43 ` David Mazieres
2015-08-24 22:14 ` Amadeusz Żołnowski
2015-08-26 6:31 ` Amadeusz Żołnowski
[not found] ` <87vbbwnbb4.fsf@freja.aidecoe.name>
[not found] ` <87io7wr50y.fsf@ta.scs.stanford.edu>
2015-08-31 11:59 ` Amadeusz Żołnowski
2015-08-31 17:27 ` dm-list-email-notmuch
2015-08-31 22:11 ` Amadeusz Żołnowski
2015-08-31 23:43 ` David Mazieres
2015-09-01 22:52 ` Amadeusz Żołnowski
2015-09-01 23:20 ` synchronize_flags leaving files in new (was muchsync files renames) dm-list-email-notmuch
2015-09-02 21:01 ` Amadeusz Żołnowski
2015-09-02 0:37 ` muchsync files renames David Bremner
2015-09-02 0:46 ` dm-list-email-notmuch
2015-09-02 21:21 ` Amadeusz Żołnowski
2015-09-02 23:05 ` David Bremner
2015-09-09 17:49 ` Amadeusz Żołnowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fnzmqjb.fsf@freja.aidecoe.name \
--to=aidecoe@aidecoe.name \
--cc=david@tethera.net \
--cc=mazieres-sggp47c7j46624db3rharctcei@temporary-address.scs.stanford.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).