Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Jonathan Lassoff <jof@thejof.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Delete A Source From Ferret Index
Date: Tue, 05 Jan 2010 14:11:48 -0800	[thread overview]
Message-ID: <1262729470-sup-100@sfo.thejof.com> (raw)
In-Reply-To: <1262728431-sup-8471@masanjin.net>

Excerpts from William Morgan's message of Tue Jan 05 13:55:42 -0800 2010:
> In this particular case you could also have run sup-tweak-labels to add
> the spam label to everything from that source (and then edited
> sources.yaml to make it autoapply for any new messages).

Ah. Nice other way around that. Would have been an even quicker solution
in this case.

I added this recipe to the wiki:
http://sup.rubyforge.org/wiki/wiki.pl?RemovingASource

--j
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-01-05 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04  3:35 Jonathan Lassoff
2010-01-05  2:21 ` Jonathan Lassoff
2010-01-05 21:55   ` William Morgan
2010-01-05 22:11     ` Jonathan Lassoff [this message]
2010-01-05 22:45       ` William Morgan

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=1262729470-sup-100@sfo.thejof.com \
    --to=jof@thejof.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