Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: daniel@wagner-home.com (Daniel Wagner)
Subject: [sup-talk] migrating email to a new computer
Date: Wed, 19 Nov 2008 17:50:39 -0500	[thread overview]
Message-ID: <1227135030-sup-401@buckwheat> (raw)

Hey all, I've got a quick question about how sup handles Maildir.  I'm
going to be migrating to a new machine soon, and I've got a couple of
questions about it.

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 know that Maildir
   uses unique names, so this shouldn't clobber any messages, but I
   haven't seen any information on whether this could cause other kinds
   of problems.
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.
   I guess this probably interacts with the previous question, too; in
   the end, I would much prefer to keep my metadata than to merge
   Maildir directories if they are mutually exclusive.
3. I'm assuming I won't lose anything if I update sup.

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.

Thanks!
~d


             reply	other threads:[~2008-11-19 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 22:50 Daniel Wagner [this message]
2008-11-27  0:05 ` William Morgan
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=1227135030-sup-401@buckwheat \
    --to=daniel@wagner-home.com \
    /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