--- /dev/null
+Return-Path: <tomi.ollila@iki.fi>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 6538B6DE02B0\r
+ for <notmuch@notmuchmail.org>; Tue, 31 May 2016 22:04:42 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.579\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.579 tagged_above=-999 required=5 tests=[AWL=-0.073,\r
+ SPF_NEUTRAL=0.652] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id kpeLF88mx5RB for <notmuch@notmuchmail.org>;\r
+ Tue, 31 May 2016 22:04:33 -0700 (PDT)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 675286DE02AD\r
+ for <notmuch@notmuchmail.org>; Tue, 31 May 2016 22:04:33 -0700 (PDT)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+ by guru.guru-group.fi (Postfix) with ESMTP id 9954910008E;\r
+ Wed, 1 Jun 2016 08:04:17 +0300 (EEST)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
+ David Bremner <david@tethera.net>, notmuch@notmuchmail.org\r
+Subject: Re: [RFC2 Patch 5/5] lib: iterator API for message properties\r
+In-Reply-To: <87pos1u14p.fsf@alice.fifthhorseman.net>\r
+References: <1463927339-5441-1-git-send-email-david@tethera.net>\r
+ <1464608999-14774-1-git-send-email-david@tethera.net>\r
+ <1464608999-14774-6-git-send-email-david@tethera.net>\r
+ <8760tthfuy.fsf@zancas.localnet> <87pos1u14p.fsf@alice.fifthhorseman.net>\r
+User-Agent: Notmuch/0.22+32~gd4854c5 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Wed, 01 Jun 2016 08:04:17 +0300\r
+Message-ID: <m2oa7lcxf2.fsf@guru.guru-group.fi>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 01 Jun 2016 05:04:42 -0000\r
+\r
+On Wed, Jun 01 2016, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
+\r
+> On Tue 2016-05-31 21:12:21 -0400, David Bremner <david@tethera.net> wrote:\r
+>> I was thinking a bit about how to dump/restore these.\r
+>>\r
+>> The most upwardly compatible way that i thought of is something like\r
+>>\r
+>> #=3D msg-id key=3Dval key=3Dval\r
+>>\r
+>> i.e. duplicate the msg-id for messages with properties\r
+>>\r
+>> This would be ignored by old notmuch-restore.\r
+>>\r
+>> Otherwise, maybe something like\r
+>>\r
+>> msg-id -- +tag +tag # key=3Dval key=3Dval\r
+>>\r
+>> I'm not sure. this might crash old notmuch-restore.\r
+>>\r
+>> How important is backward compatibility, and how important is minimizing\r
+>> dump size? It's a bit hard to predict the things people might use\r
+>> message properties for, but for thread surgery, I would expect a small\r
+>> number of messages with properties.\r
+>\r
+> The other concern is our conception of how properties are unset/removed,\r
+> right?\r
+>\r
+> With tags, it's possible to include -blah to remove the tag "blah". how\r
+> do we remove/clear/overwrite these tags? what about using +key=3Dval or\r
+> -key=3Dval to set/unset certain key/value combinations, and a value-less\r
+> key=3D to remove all values matching a given key?\r
+>\r
+> alternately:\r
+>\r
+> key=3Dval (clears all values for "key", and sets a new value "val")\r
+> key+=3Dval (appends a value "val" for "key")\r
+> key-=3Dval (removes any "key" set to "val")\r
+> key=3D (clears all values for "key"\r
+\r
+We'd have to distinct between key being empty and unset,\r
+comparable to how notmuch config behaves...\r
+\r
+\r
+$ notmuch config get built_with.compact\r
+true\r
+$\r
+$ notmuch config get search.exclude_tag\r
+$\r
+$ notmuch config get search.exclude_tagsz=20\r
+Unknown configuration item: search.exclude_tagsz\r
+zsh: exit 1 notmuch config get search.exclude_tagsz\r
+\r
+>\r
+> ---------\r
+>\r
+> However we resolve this particular decision, it'd be nice to have a\r
+> stable, sane story about backward compatibility going forward, so that\r
+> we don't have to worry about it in the future.\r
+>\r
+> For example, each dump file could start with a line like:\r
+>\r
+> #version 1\r
+>\r
+> and notmuch restore would assume that without "#version n" as the first\r
+> line, it's version 0. then notmuch restore could decline to parse dump\r
+> files of a version that it doesn't know about.\r
+>\r
+> Alternately, we could have the first line be something like:\r
+>\r
+> #features config properties\r
+>\r
+> and if the first line is not #features, then we assume that no features\r
+> are in place -- but if restore sees features it doesn't know about, it\r
+> can offer to proceed while warning the user that we might miss something\r
+> (or that something might break).\r
+\r
+Currently dump output starts with (just run notmuch dump | less)\r
+\r
+#notmuch-dump batch-tag:2 config,tags\r
+\r
+perhaps this info could be put there -- is restore now (since a few notmuch\r
+versions) already declining if this contains some strange data ?\r
+\r
+of the 2 above suggestions I'd go w/ compatibilty version; it might be\r
+challenging to get old notmuch parse relevant data from newer format...\r
+... unless we also change the format to something more structured (jso^H^H^=\r
+H^G\r
+where only known data can be extracted (no, it is not SMOP, NO!)\r
+\r
+> Thanks for working on this, David! I think this is going to be really\r
+> useful!\r
+\r
+=C3=96h, what is this feature for... >;) maybe I have to look into the seri=\r
+es\r
+deeper...\r
+\r
+>\r
+> --dkg\r
+\r
+Tomi\r
projects / notmuch-archives.git / commitdiff