unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: martin f krafft <madduck@madduck.net>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch and imap [musing, no code :)]
Date: Fri, 8 Jan 2010 16:00:20 +1300	[thread overview]
Message-ID: <20100108030019.GC23442@lapse.rw.madduck.net> (raw)
In-Reply-To: <87ljh3cb1j.fsf@pivot.cs.unb.ca>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

also sprach David Bremner <david@tethera.net> [2009.12.17.0218 +1300]:
> I agree that the labels-in-headers approach has some nice
> advantages.  I haven't thought through merging of tag lists, but
> maybe that is no worse than other approaches.  One thing that
> worries me a bit is that notmuch updates tags often, and each of
> these updates would require rewriting the message, at least in the
> obvious implementation.

If we separated implicit and explicit tags, then that issue would
not exist, and from all I can tell, only the privacy issues, and the
risk of losing mail when files are rewritten persist.

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
DISCLAIMER: this entire message is privileged communication, intended
for the sole use of its recipients only. If you read it even though
you know you aren't supposed to, you're a poopy-head.
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2010-01-08  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 12:05 notmuch and imap [musing, no code :)] David Bremner
2009-12-16  0:54 ` Alec Berryman
2009-12-16 13:18   ` David Bremner
2009-12-16 14:29     ` Marten Veldthuis
2010-01-08  3:00     ` martin f krafft [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=20100108030019.GC23442@lapse.rw.madduck.net \
    --to=madduck@madduck.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).