From: Sascha Silbe <sascha-ml-reply-to-2011-1@silbe.org>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>
Cc: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] add sup-import-dump: import message state in sup-dump format
Date: Fri, 21 Jan 2011 13:36:35 +0100 [thread overview]
Message-ID: <1295612176-sup-1890@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <4d385491.2308e30a.02b2.ffffd7ce@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
Excerpts from Nicolas Pouillard's message of Thu Jan 20 16:28:17 +0100 2011:
> So it does not clear the index, right? It only assign the set of labels to the
> given message. Just what I need to upgrade my sup index with my notmuch index.
Yes, that's exactly the purpose (except that I'm using it to synchronise
two sup installations, not sup and notmuch).
> > It should also be easy enough to add support for a "diff" style format that
> > would allow replaying "logs" if sup were enhanced to write those in the
> > future.
> Please do.
Eventually I will, but I don't know when I'll get around to do it.
> I hacked such a logging feature [1] in the past [...]
Nice! Looks like the only other places (besides sync_message) that write
to the index are delete and delete_message (the latter is part of a
not-yet-upstreamed patch of mine). Looks like the hardest part will
actually be adding the configuration option for the file name (with
support for a date template). ;)
> [1]: http://gitorious.org/~ertai/sup/clone-by-ertai/commits/to-submit-log-labels-mapping
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-01-21 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 9:13 [sup-devel] alternative for sup-sync option --restored? Sascha Silbe
2010-08-22 13:40 ` Sascha Silbe
2011-01-19 13:52 ` [sup-devel] [PATCH] add sup-import-dump: import message state in sup-dump format Sascha Silbe
2011-01-20 4:13 ` Rich Lane
2011-01-20 15:28 ` Nicolas Pouillard
2011-01-21 12:36 ` Sascha Silbe [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295612176-sup-1890@xo15-sascha.sascha.silbe.org \
--to=sascha-ml-reply-to-2011-1@silbe.org \
--cc=nicolas.pouillard@gmail.com \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox