From: David Bremner <david@tethera.net>
To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>
Subject: Re: Bug: notmuch new chokes on dangling symlinks and quits
Date: Mon, 27 Jan 2014 13:40:14 -0400 [thread overview]
Message-ID: <878uu1l3wh.fsf@zancas.localnet> (raw)
In-Reply-To: <20140127011427.GD10844@boo.workgroup>
Gregor Zattler <telegraph@gmx.net> writes:
> Hi David,
> * David Bremner <david@tethera.net> [26. Jan. 2014]:
>> Gregor Zattler <telegraph@gmx.net> writes:
>>> I consider this to be a bug. Instead notmuch should simply
>>> ignore the symlink.
>>>
>>
>> Since there is a test for specifically this behaviour, I'd have to say
>> it's a design decision you don't agree with, not a bug ;).
>
> May I ask why this is so?
>
Purely from memory (I wasn't involved, and didn't dig up the the
discussion):
- a common use case is linking different trees into one notmuch-index
tree.
- if a subtree disappears (e.g. by a network failure), then the choices
are stop the index or ignore the missing files.
- in the latter case, all tags from "deleted" messages are lost
So, a simple solution which avoids data loss is to abort the index
process.
A more complicated solution would be possible of course, but nobody
proposed it (or more importantly, did it) yet.
d
prev parent reply other threads:[~2014-01-27 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 13:18 Bug: notmuch new chokes on dangling symlinks and quits Gregor Zattler
2014-01-26 16:43 ` David Bremner
2014-01-27 1:14 ` Gregor Zattler
2014-01-27 15:55 ` Eric
2014-01-27 17:40 ` David Bremner [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=878uu1l3wh.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=telegraph@gmx.net \
/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).