From: Keith Packard <keithp@keithp.com>
To: Mikhail Gusarov <dottedmag@dottedmag.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Handle rename of message file
Date: Wed, 18 Nov 2009 19:12:50 -0800 [thread overview]
Message-ID: <yuny6m32onh.fsf@aiko.keithp.com> (raw)
In-Reply-To: <87pr7f1cxr.fsf@vertex.dottedmag>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Thu, 19 Nov 2009 08:11:12 +0600, Mikhail Gusarov <dottedmag@dottedmag.net> wrote:
>
> Twas brillig at 18:06:09 18.11.2009 UTC-08 when keithp@keithp.com did gyre and gimble:
>
> KP> Checking for new files is easy; notmuch already does that, and so
> KP> handling renames doesn't seem all that difficult.
>
> Except rename does not change mtime of file, and so it won't be picked
> up by 'notmuch new'.
Yeah, good point -- notmuch new doesn't make sure each file it finds is
already in the database. Again, some kind of inotify-based daemon would
make that efficient, while starting up that daemon could take some time
while the database was searched for new or missing files.
Alternatively, we could record the contents of the directory after
scanning it and then use that to track file changes. It seems like the
current database just doesn't have enough information to make this
tractable.
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2009-11-19 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 20:51 [PATCH] Handle rename of message file Mikhail Gusarov
2009-11-19 1:08 ` Carl Worth
2009-11-19 1:14 ` Mikhail Gusarov
2009-11-19 2:06 ` Keith Packard
2009-11-19 2:11 ` Mikhail Gusarov
2009-11-19 3:12 ` Keith Packard [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=yuny6m32onh.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=dottedmag@dottedmag.net \
--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).