From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH v2 0/6] batch tagging support: "notmuch tag --stdin"
Date: Sat, 14 Apr 2012 13:27:06 -0700 [thread overview]
Message-ID: <87d37ays85.fsf@servo.finestructure.net> (raw)
In-Reply-To: <cover.1334404979.git.jani@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Sat, Apr 14 2012, Jani Nikula <jani@nikula.org> wrote:
> This series adds support for batch tagging through stdin to "notmuch
> tag". This should be useful and efficient for e.g. initial tagging
> scripts. Also, this adds locking around a batch of tag changes, which is
> also useful for initial tagging scripts. See the test patch for an
> example using a "here document".
My issues from v1 still stand. I would rather see some unification with
the existing tag file format, rather than introduce a second format,
with it's increased maintenance burden and confusion to users. Either
that or a more general batch command interface.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-04-14 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 12:15 [PATCH v2 0/6] batch tagging support: "notmuch tag --stdin" Jani Nikula
2012-04-14 12:15 ` [PATCH v2 1/6] hex-escape: (en|de)code strings to/from restricted character set Jani Nikula
2012-04-14 12:15 ` [PATCH v2 2/6] test/hex-xcode: new test binary Jani Nikula
2012-04-14 12:15 ` [PATCH v2 3/6] test/hex-escaping: new test for hex escaping routines Jani Nikula
2012-04-14 12:15 ` [PATCH v2 4/6] cli: add support for batch tagging operations to "notmuch tag" Jani Nikula
2012-04-14 12:15 ` [PATCH v2 5/6] test: add test for notmuch tag --stdin option Jani Nikula
2012-04-14 12:15 ` [PATCH v2 6/6] man: document " Jani Nikula
2012-04-14 20:27 ` Jameson Graef Rollins [this message]
2012-04-14 21:07 ` [PATCH v2 0/6] batch tagging support: "notmuch tag --stdin" Jani Nikula
2012-04-15 12:02 ` David Bremner
2012-04-18 18:58 ` Jani Nikula
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=87d37ays85.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=jani@nikula.org \
--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).