Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>,
	sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Old Mail
Date: Wed, 27 Jan 2010 02:34:14 -0800 (PST)	[thread overview]
Message-ID: <4b6016a6.0d67f10a.74f7.ffffed83@mx.google.com> (raw)
In-Reply-To: <1264527747-sup-6577@masanjin.net>

On Tue, 26 Jan 2010 12:47:41 -0500, William Morgan <wmorgan-sup@masanjin.net> wrote:
> Reformatted excerpts from Michael McDermott's message of 2010-01-26:
> > I have sup 0.10 running off of Maildirs fed by offlineimap. Naturally,
> > when I first set this up, I had a great deal of old mail pulled, mail
> > that sup has left marked as unread. Is there anyway to mark all of
> > these older messages read, short of searching for is:unread, tagging a
> > screenful, and marking them read, and doing this through several years
> > worth of email?
> 
> Try sup-tweak-labels, e.g.:
> 
>   sup-tweak-labels -q is:unread -r unread -v -n --all-sources

It reminds me that I would really like an option to sup-tweak-labels to accept
a file in the dump format.

It would allow us to feed a "diff" in dump format and so be able to recover
quickly incrementally upgrade a sup index.

NOTE: using sup-sync is not an option, it is way too slow to look at every
messages of every sources.

Cheers,

-- 
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2010-01-27 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 16:14 Michael McDermott
2010-01-26 17:47 ` William Morgan
2010-01-26 19:16   ` Michael McDermott
2010-01-27 10:34   ` Nicolas Pouillard [this message]
2010-01-27 13:32     ` William Morgan
2010-01-27 14:39       ` Nicolas Pouillard

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=4b6016a6.0d67f10a.74f7.ffffed83@mx.google.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=sup-talk@rubyforge.org \
    --cc=wmorgan-sup@masanjin.net \
    /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