--- /dev/null
+Return-Path: <jani@nikula.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 05E60431FB6\r
+ for <notmuch@notmuchmail.org>; Mon, 2 Apr 2012 14:07:40 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+ tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id d7ZL+kMrJkhd for <notmuch@notmuchmail.org>;\r
+ Mon, 2 Apr 2012 14:07:39 -0700 (PDT)\r
+Received: from mail-pb0-f53.google.com (mail-pb0-f53.google.com\r
+ [209.85.160.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 2C9E9431FAE\r
+ for <notmuch@notmuchmail.org>; Mon, 2 Apr 2012 14:07:39 -0700 (PDT)\r
+Received: by pbcuo1 with SMTP id uo1so5525664pbc.26\r
+ for <notmuch@notmuchmail.org>; Mon, 02 Apr 2012 14:07:38 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=google.com; s=20120113;\r
+ h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
+ :cc:content-type:x-gm-message-state;\r
+ bh=K0lWuLMCbW08EidSK5qhMzZSCQgtSzrH+awnJPThNpc=;\r
+ b=UXON5g+cgx+0//PFDEkWirHtlpm7RhjlHZMm3+eOV3m0gt5I9o5QjQIfuzXfD7t3zj\r
+ YbKMe8vae+K8GyxY3HQaHKENe8lWWMewe/Qy4jcznRD43kj/+nlKeJZIQtpRbugP0vDO\r
+ RtxZSqI3JZAlaQsR+nTv8ePSkacjEhtF8PmqhLgPNRZA33670EmcQH2bOLYSa252EHPd\r
+ TWsLWVkxQ443ivyhunldIN5wYzrt37yHVHR6S9/f+0dLBPcKXvMbkJheM3HemAcR6z2F\r
+ Fzyi8RSQArBaAlRVTVbEeT576qkr7Rm2ssl1ui9L+46UdDFXS/6fV2keH8LDyN/UCGTx\r
+ d1AA==\r
+MIME-Version: 1.0\r
+Received: by 10.68.202.195 with SMTP id kk3mr23240520pbc.96.1333400858147;\r
+ Mon, 02 Apr 2012 14:07:38 -0700 (PDT)\r
+Received: by 10.68.231.104 with HTTP; Mon, 2 Apr 2012 14:07:37 -0700 (PDT)\r
+Received: by 10.68.231.104 with HTTP; Mon, 2 Apr 2012 14:07:37 -0700 (PDT)\r
+In-Reply-To: <87iphh50hz.fsf@servo.finestructure.net>\r
+References: <cover.1333231401.git.jani@nikula.org>\r
+ <f360a40bed50208d146aee8b06946b1b8315e818.1333231401.git.jani@nikula.org>\r
+ <87ty123tpc.fsf@servo.finestructure.net>\r
+ <87aa2tc22z.fsf@zancas.localnet>\r
+ <87iphh50hz.fsf@servo.finestructure.net>\r
+Date: Tue, 3 Apr 2012 00:07:37 +0300\r
+Message-ID:\r
+ <CAB+hUn_J9oOmbWaQ+_2yGG6i6ecDXbfJWYbpaYx_kbSnAH+EcA@mail.gmail.com>\r
+Subject: Re: [PATCH 6/8] cli: add support for batch tagging operations to\r
+ "notmuch tag"\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>\r
+Content-Type: multipart/alternative; boundary=047d7b15b1077e3c0c04bcb89424\r
+X-Gm-Message-State:\r
+ ALoCoQmPpnoDWPkx8LvRtTcUUgONe0ZOeRYd1+7dVfyh4s33w6TrazmMhv27FexAxVirSJZicLje\r
+Cc: Notmuch Mail <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://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: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 02 Apr 2012 21:07:40 -0000\r
+\r
+--047d7b15b1077e3c0c04bcb89424\r
+Content-Type: text/plain; charset=UTF-8\r
+\r
+On Apr 2, 2012 11:42 PM, "Jameson Graef Rollins" <jrollins@finestructure.net>\r
+wrote:\r
+>\r
+> On Mon, Apr 02 2012, David Bremner <david@tethera.net> wrote:\r
+> > Jameson Graef Rollins <jrollins@finestructure.net> writes:\r
+> >> On Sat, Mar 31 2012, Jani Nikula <jani@nikula.org> wrote:\r
+> >>> Add support for batch tagging operations through stdin to "notmuch\r
+> >>> tag". This can be enabled with the new --stdin command line option to\r
+> >>> "notmuch new". The input must consist of lines of the format:\r
+> >>>\r
+> >>> T +<tag>|-<tag> [...] [--] <search-terms>\r
+> >>\r
+> >\r
+> > I think that's my fault. I was imagining a possible future line-oriented\r
+> > notmuch server and having various actions/queries possible. It seems a\r
+> > bit blue sky at this point, but it does give extesibility fairly\r
+> > cheaply.\r
+>\r
+> But then why not just make the command explicit, and just have the first\r
+> field be "tag"?\r
+>\r
+> But then I wonder why do we even need any of this at all? Isn't it this\r
+> just exactly equivalent to:\r
+>\r
+> xargs -l notmuch <commands.txt\r
+>\r
+> ??\r
+\r
+Batch tagging brings performance and atomicity by opening and closing the\r
+db only once. The hex encoding handles insane message ids and tags.\r
+Otherwise there should be no difference.\r
+\r
+Jani.\r
+\r
+>\r
+> jamie.\r
+\r
+--047d7b15b1077e3c0c04bcb89424\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<p><br>\r
+On Apr 2, 2012 11:42 PM, "Jameson Graef Rollins" <<a href=3D"m=\r
+ailto:jrollins@finestructure.net">jrollins@finestructure.net</a>> wrote:=\r
+<br>\r
+><br>\r
+> On Mon, Apr 02 2012, David Bremner <<a href=3D"mailto:david@tethera=\r
+.net">david@tethera.net</a>> wrote:<br>\r
+> > Jameson Graef Rollins <<a href=3D"mailto:jrollins@finestructur=\r
+e.net">jrollins@finestructure.net</a>> writes:<br>\r
+> >> On Sat, Mar 31 2012, Jani Nikula <<a href=3D"mailto:jani@n=\r
+ikula.org">jani@nikula.org</a>> wrote:<br>\r
+> >>> Add support for batch tagging operations through stdin to=\r
+ "notmuch<br>\r
+> >>> tag". This can be enabled with the new --stdin comma=\r
+nd line option to<br>\r
+> >>> "notmuch new". The input must consist of lines =\r
+of the format:<br>\r
+> >>><br>\r
+> >>> T +<tag>|-<tag> [...] [--] <search-terms&g=\r
+t;<br>\r
+> >><br>\r
+> ><br>\r
+> > I think that's my fault. I was imagining a possible future li=\r
+ne-oriented<br>\r
+> > notmuch server and having various actions/queries possible. It se=\r
+ems a<br>\r
+> > bit blue sky at this point, but it does give extesibility fairly<=\r
+br>\r
+> > cheaply.<br>\r
+><br>\r
+> But then why not just make the command explicit, and just have the fir=\r
+st<br>\r
+> field be "tag"?<br>\r
+><br>\r
+> But then I wonder why do we even need any of this at all? =C2=A0Isn=\r
+9;t it this<br>\r
+> just exactly equivalent to:<br>\r
+><br>\r
+> xargs -l notmuch <commands.txt<br>\r
+><br>\r
+> ??</p>\r
+<p>Batch tagging brings performance and atomicity by opening and closing th=\r
+e db only once. The hex encoding handles insane message ids and tags. Other=\r
+wise there should be no difference.</p>\r
+<p>Jani.</p>\r
+<p>><br>\r
+> jamie.<br>\r
+</p>\r
+\r
+--047d7b15b1077e3c0c04bcb89424--\r