From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Configuration problems with sup [2]
Date: Tue, 15 Apr 2008 09:26:43 -0700 [thread overview]
Message-ID: <1208276624-sup-9670@south> (raw)
In-Reply-To: <0E731DC9-3C5D-4A1C-909A-2949977D0F71@hinterland.nu>
Reformatted excerpts from Christopher Marsh's message of 2008-04-14:
> Incidentally, the 974 messages sup was showing were the consequence of
> a previous attempt to get it working. The mailbox referred to in the
> error log has ~20,000 messages in it. I considered deleting the index,
> but couldn't find it.
It's in ~/.sup/ferret. If you have no labels you want to keep, you can
delete that directory and sup-sync --all --all-sources to rebuild it.
Once your sources.yaml problem is fixed, of course. :)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-04-15 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 6:18 Christopher Marsh
2008-04-15 16:26 ` William Morgan [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=1208276624-sup-9670@south \
--to=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