From: Tomi Ollila <tomi.ollila@iki.fi>
To: Notmuch Mailing List <notmuch@notmuchmail.org>
Subject: Re: [RFC/PATCH] notmuch link
Date: Thu, 06 Oct 2011 17:42:12 +0300 [thread overview]
Message-ID: <yf6lisy2ncr.fsf@taco2.nixu.fi> (raw)
In-Reply-To: <20111003211522.GB28273@hayalet> (Ali Polatel's message of "Tue, 4 Oct 2011 00:15:22 +0300")
On Tue 04 Oct 2011 00:15, Ali Polatel <polatel@gmail.com> writes:
> Ali Polatel yazmış:
>>
>>This mail is merely a request for comments and testing.
>
> Sigh...
> I have just noticed "notmuch show" learned --format=mbox which makes
> this patch rather pointless for me. This changeset will keep living
> under my notmuch repository possibly without receiving any updates.
>
>>Ali Polatel (1):
>> link: Add new command
The 'link' feature would have been pretty cool as the linking goes
blazingly fast. But, the unfortunate side effect of this would be
that if the file referenced by link is modified, the original file gets
modified.I personally don't want this to happen after the mail is delivered
unless I intentionally do it (my delivered mails filenames are generated
from the md5sum of the original content, so re-comparing all content
will reveal what files been modified :D)
If one of the goals of notmuch is to not to change the contents of mail
files and avoid this happening accidentally by other programs (referencing
files in configured 'path' from other programs considered non-accidental
action) then this feature should just be dropped (but not forgotten so it
doesn't get re-implemented).
> -alip
Tomi
prev parent reply other threads:[~2011-10-06 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 8:45 [RFC/PATCH] notmuch link Ali Polatel
2011-10-01 8:45 ` [RFC/PATCH] link: Add new command Ali Polatel
2011-10-03 21:15 ` [RFC/PATCH] notmuch link Ali Polatel
2011-10-06 14:42 ` Tomi Ollila [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=yf6lisy2ncr.fsf@taco2.nixu.fi \
--to=tomi.ollila@iki.fi \
--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).