From: Carl Worth <cworth@cworth.org>
To: Jed Brown <jed@59A2.org>, Tassilo Horn <tassilo@member.fsf.org>,
Mikhail Gusarov <dottedmag@dottedmag.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Notmuch doesn't index new mails when mail location contains symlinks
Date: Thu, 26 Nov 2009 13:14:22 -0800 [thread overview]
Message-ID: <87ljhtq98x.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <873a41dtbu.fsf@59A2.org>
On Thu, 26 Nov 2009 19:39:01 +0100, Jed Brown <jed@59A2.org> wrote:
> On Thu, 26 Nov 2009 10:34:12 -0800, Carl Worth <cworth@cworth.org> wrote:
> > I'm a little confused here. Notmuch only uses stat, so it should be
> > looking at the target's mtime already. It actually takes special effort
> > (via lstat) to get at the mtime of the link itself.
> >
> > So why aren't things just working?
>
> Because mtime doesn't change on the directory *above* the symlinks.
>
> I think.
Then I'm still being really dense here. The non-propagation of mtime is
the with actual directories. And the code is trying to do the right
thing for that.
So I still don't see what's being different with the symlinks. I should
probably stop exposing ignorance here on the list, and just sit down
with symlinks in a mail store and see what's happening.
-Carl
next prev parent reply other threads:[~2009-11-26 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 10:49 Notmuch doesn't index new mails Tassilo Horn
2009-11-23 13:55 ` Notmuch doesn't index new mails when mail location contains symlinks (was: Notmuch doesn't index new mails) Tassilo Horn
2009-11-23 14:02 ` Notmuch doesn't index new mails when mail location contains symlinks Mikhail Gusarov
2009-11-23 14:43 ` Tassilo Horn
2009-11-23 15:01 ` Tassilo Horn
2009-11-23 15:10 ` Mikhail Gusarov
2009-11-23 15:16 ` Jed Brown
2009-11-23 15:03 ` Jed Brown
2009-11-23 15:11 ` Mikhail Gusarov
2009-11-26 18:34 ` Carl Worth
2009-11-26 18:39 ` Jed Brown
2009-11-26 21:14 ` Carl Worth [this message]
2009-11-26 21:22 ` Jed Brown
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=87ljhtq98x.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=dottedmag@dottedmag.net \
--cc=jed@59A2.org \
--cc=notmuch@notmuchmail.org \
--cc=tassilo@member.fsf.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).