From: David Bremner <david@tethera.net>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] Outline fix for emacs tagging race
Date: Fri, 09 Nov 2012 19:27:40 -0400 [thread overview]
Message-ID: <87625e2w7n.fsf@zancas.localnet> (raw)
In-Reply-To: <1352487491-31512-1-git-send-email-markwalters1009@gmail.com>
Mark Walters <markwalters1009@gmail.com> writes:
> I can think of several possible solutions (e.g., batch it in my new
> stuff, put some batching in notmuch-tag, all notmuch tag to read a
> query from stdin). But before any larger more intrusive change do
> people like the general approach? Does anyone have a good way to get
> round the command line size problem?
Jani posted some patches to do batch tagging from stdin. I guess the
last full series posted was at id:cover.1334404979.git.jani@nikula.org
I believe Jani has slightly updated (or at least rebased) the patches in
git. I reworked and re-posted some of the foundational parts of the
series at id:1345382314-5330-1-git-send-email-david@tethera.net
I want to have some of this infrastucture for a new style of
backup/restore, and it's possible that batch tagging would also speed up
nmbug.
d
next prev parent reply other threads:[~2012-11-09 23:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 18:58 [PATCH 0/3] Outline fix for emacs tagging race Mark Walters
2012-11-09 18:58 ` [PATCH 1/3] test: test for race when tagging from emacs search Mark Walters
2012-11-09 18:58 ` [PATCH 2/3] cli: all search mode to include msg-ids with JSON output Mark Walters
2012-11-22 16:15 ` Jameson Graef Rollins
2012-11-22 18:05 ` Michal Nazarewicz
2012-11-22 19:35 ` Mark Walters
2012-11-23 7:23 ` Jameson Graef Rollins
2012-11-23 9:01 ` Tomi Ollila
2012-11-23 20:39 ` Austin Clements
2012-11-09 18:58 ` [PATCH 3/3] emacs: make emacs use message-ids for tagging Mark Walters
2012-11-09 21:25 ` [PATCH 0/3] Outline fix for emacs tagging race Tomi Ollila
2012-11-09 23:27 ` David Bremner [this message]
2012-11-10 5:29 ` Austin Clements
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=87625e2w7n.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=markwalters1009@gmail.com \
--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).