Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Mr. (Mr.)
Subject: [sup-talk] migrating email to a new computer
Date: Mon, 08 Dec 2008 00:33:34 -0500	[thread overview]
Message-ID: <1228714133-sup-9592@buckwheat> (raw)
In-Reply-To: <1228710381-sup-9800@buckwheat>

Excerpts from Daniel Wagner's message of Mon Dec 08 00:14:39 -0500 2008:
> The Numbers According To sup-sync
> entries in the dump file    26462
> entries scanned             24779
> entries added               24373
> warnings                       27
> fakes                          75
> 
> The Numbers According To sup
>                             old machine     new machine
> messages in the index       26459           24416

Ah, I just realized: copying everything to one directory is fine only if
the filenames have unique names.  A quick investigation shows I probably
nuked around 500-600 messages with this assumption, so that's one easily
fixable problem.  But that still leaves ~1500 messages in the aether...

Love!
~d


  reply	other threads:[~2008-12-08  5:33 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
2008-12-08  5:14   ` Daniel Wagner
2008-12-08  5:33     ` Mr. [this message]
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=1228714133-sup-9592@buckwheat \
    --to=sup-talk@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