From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Sup finds ghost messages
Date: Wed, 14 Oct 2009 16:34:55 +0300 [thread overview]
Message-ID: <1255526768-sup-3152@tilus.net> (raw)
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.
I'm 100% sure I did not have any sup-talk mails from somewhere
2007-2008 in any of my other sources. Still sup-sync said it did not
add a couple of messages which supposedly already were in the index.
ps. Happily on sup now. \o/ All mails in, 1G index. Xapian is
blazing fast...
pps. Why bugs to this list? Why not use a tracker? (besides that sup
is awesome tracker too ;)
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-10-14 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 13:34 Tero Tilus [this message]
2009-10-15 13: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=1255526768-sup-3152@tilus.net \
--to=tero@tilus.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