Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] [Heliotrope] What exactly does reordering do? Is it still necessary?
Date: Wed, 22 Feb 2012 23:00:27 +0100	[thread overview]
Message-ID: <1329947900-sup-5773@stapelberg.de> (raw)

Hi,

I just realized that I forgot to import the maildir in which I store my sent
messages. After adding them to heliotrope, do I have to reorder the index? What
exactly does it do and why is that necessary?

I’m a bit confused because commit
https://github.com/wmorgan/heliotrope/commit/f7bfda9dd83db1b9cd2a51ba2599da81fc1b87c1
talks about "reindex without --reorder".

Best regards,
Michael

PS: The real time it takes to reorder my index is about 1 hour and 30 minutes :(
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

             reply	other threads:[~2012-02-22 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 22:00 Michael Stapelberg [this message]
2012-02-23  6:39 ` 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=1329947900-sup-5773@stapelberg.de \
    --to=michael+sup@stapelberg.de \
    --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