From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] [PATCH] remove use of Object#tap
Date: Sun, 30 Aug 2009 20:50:46 -0400 [thread overview]
Message-ID: <1251677009-sup-2661@zyrg.net> (raw)
In-Reply-To: <1251676342-sup-7038@ntdws12.chass.utoronto.ca>
Excerpts from Ben Walton's message of Sun Aug 30 19:55:56 -0400 2009:
> Excerpts from Blake Burkhart's message of Sun Aug 30 17:50:09 -0400 2009:
>
> > I got it to work. Mostly a least. What does a sup-dump file actually store? I
> > lost all read/unread statuses and all labels (including the spam label thing,
> > I assume it's just a normal label).
>
> I also lost labels on my first attempt at switching to xapian. I gave
> up for a few days as there were other issues with labels at the time.
> Losing labels during the switch would be a deal breaker, but I assume
> this isn't intended (as that would be madness, madness, I say)...is
> there a step I'm missing in the following (assuming HEAD of next)?
>
> 4. cp ~/.sup/sources.yaml{,.bak}
> 5. ruby -Ilib bin/sup-dump > dumpfile
> 6. SUP_INDEX=xapian ruby -Ilib bin/sup-sync --all --all-sources
> --restore dumpfile
> 7. SUP_INDEX=xapian ruby -Ilib bin/sup -o
>
> Thanks
> -Ben
>
This is an issue that was introduced in 906ab35e. I've just resent a
patch for it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: restore-state-fix
Type: application/octet-stream
Size: 3534 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090830/5be2a745/attachment.obj>
next prev parent reply other threads:[~2009-08-31 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 20:28 Rich Lane
2009-08-30 20:45 ` Blake Burkhart
2009-08-30 21:50 ` Blake Burkhart
2009-08-30 23:55 ` Ben Walton
2009-08-31 0:50 ` Rich Lane [this message]
2009-09-01 3:17 ` 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=1251677009-sup-2661@zyrg.net \
--to=rlane@club.cc.cmu.edu \
/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