From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] migrating email to a new computer
Date: Wed, 26 Nov 2008 16:05:13 -0800 [thread overview]
Message-ID: <1227743600-sup-8882@entry> (raw)
In-Reply-To: <1227135030-sup-401@buckwheat>
Hi Daniel,
Sorry for the delay in replying. I've been moving across country and
only have sporadic internet access right now.
Reformatted excerpts from Daniel Wagner's message of 2008-11-19:
> 1. My mail is spread out in hundreds of Maildir directories, most of
> them "legacy" directories that I want to merge as I migrate. Can I do
> this by just copying the mail files from the various "new" and "cur"
> directories to a central "cur" directory?
I *think* that just moving files from cur/ to cur/ and new/ to new/ will
work, but moving from new/ to cur/ I think typically changes the
filename slightly. I don't know if the rename is required or optional
though. Sup certainly doesn't care, but other tools might.
> 2. A more sup-related question: what things do I need to copy to
> migrate my labels, read/archived/starred status information, etc? I
> definitely want to maintain as much of my mail's metadata as I can.
Since you're doing lots of moving things around, combining sources, and
upgrading Sup at the same time, I think the best option is going to be
to rebuild your index from scratch. You can use sup-dump to dump out
state information into a huge text file, and sup-sync --restored
--restore should be able to make use of that information to keep your
message state once your new sources have been created.
But definitely, DEFINITELY test it out first. I haven't tried that stuff
for a while and it might have experienced bitrot.
> 3. I'm assuming I won't lose anything if I update sup.
Nope. And I can't believe you're still using Sup 0.4!
> I think this topic deserves a wiki page, so I'll write up a summary of
> any advice I get as well as how my experience goes for future
> posterity.
That sounds great. Let us know how it goes, and I'll do my best to help
you though the process if things break. Just be sure to keep a backup of
everything. Message state is a precious asset.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-11-27 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 22:50 Daniel Wagner
2008-11-27 0:05 ` William Morgan [this message]
2008-12-08 5:14 ` Daniel Wagner
2008-12-08 5:33 ` Mr.
2008-12-12 1:31 ` William Morgan
2008-11-28 2:25 ` Daniel Wagner
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=1227743600-sup-8882@entry \
--to=wmorgan-sup@masanjin.net \
/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