From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] after second heliotrope import, new messages not appearing
Date: Thu, 27 Dec 2012 16:19:40 +0000 [thread overview]
Message-ID: <CAOxvSbextWLEObcKrU-93SzFqnhZ-up7cV6MwUboFgN2TM7GNw@mail.gmail.com> (raw)
Hello
I've just been trying to carry on from where I left off with migrating
my work email into heliotrope (which I last worked on in May).
So I've rsynced the mbox files across to where I will run heliotrope
and tried running heliotrope-import to put all the new messages in the
index. It appeared to work properly, reporting that messages were
being added to the index and the index files themselves have had their
timestamps updated. But when I start turnsole, I can't find any email
after May.
Any ideas on where to start looking to work out what is going on?
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2012-12-27 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 16:19 Hamish D [this message]
2012-12-30 16:22 ` Matthieu Rakotojaona
2013-01-01 18:33 ` Hamish D
2013-01-02 20:47 ` Matthieu Rakotojaona
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=CAOxvSbextWLEObcKrU-93SzFqnhZ-up7cV6MwUboFgN2TM7GNw@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=sup-devel@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