From: David Edmondson <dme@dme.org>
To: notmuch@notmuchmail.org
Subject: multiple machine tagging
Date: Thu, 20 May 2010 09:25:42 +0100 [thread overview]
Message-ID: <87vdaj2d4p.fsf@ut.hh.sledj.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
What's the current state of the art in merging tags from multiple
machines?
In my own case the contents of the mail store can be considered
identical on the different machines. Automated tagging is mostly fine -
it can just happen on each of the machines. Any hand-added tags are a
problem, though.
dme.
--
David Edmondson, http://dme.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2010-05-20 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 8:25 David Edmondson [this message]
2010-05-20 16:28 ` multiple machine tagging Jesse Rosenthal
2014-09-15 13:49 ` David Edmondson
2014-09-15 14:14 ` W. Trevor King
2014-09-15 14:26 ` David Edmondson
2014-09-15 15:30 ` W. Trevor King
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=87vdaj2d4p.fsf@ut.hh.sledj.net \
--to=dme@dme.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).