From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup finds ghost messages
Date: Thu, 15 Oct 2009 06:45:47 -0700 [thread overview]
Message-ID: <1255612303-sup-410@masanjin.net> (raw)
In-Reply-To: <1255526768-sup-3152@tilus.net>
Reformatted excerpts from Tero Tilus's message of 2009-10-14:
> sup-sync --all (using xapian) from a new source occasionally says 1-2
> messages already were in the index, even if they most certainly
> weren't. I noticed this when I added sup-talk archives to my index.
Can you run with -v and grep to make sure those message ids don't
actually appear more than once in the mbox file? If they don't, can you
isolate a particular one and use devel/console.sh to find out where Sup
thinks the previous occurence is?
> pps. Why bugs to this list? Why not use a tracker? (besides that sup
> is awesome tracker too ;)
If there's a good one out there I'd like to hear about it. We used ditz
for a while because I hate clicking the mouse, but eventually it became
too much effort.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-10-15 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 13:34 Tero Tilus
2009-10-15 13:45 ` 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=1255612303-sup-410@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@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