From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Sup Backtrace While Polling
Date: Tue, 12 Aug 2008 20:15:51 -0700 [thread overview]
Message-ID: <1218597311-sup-7061@entry> (raw)
In-Reply-To: <1218400279-sup-8057@tomsk>
Reformatted excerpts from Marcus Williams's message of 2008-08-10:
> On 10.8.2008, Nicolas Pouillard wrote:
> > BTW another question, how can I split my mbox file and sync sup
> > again?
>
> Use ruby and rmail ;)
[snip]
> Use sup-dump before you split, and then restore from that after you
> set up all the mboxes as your new sources with sup-add.
Yep, this is pretty much what I would recommend too.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-08-13 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 9:53 Nicolas Pouillard
2008-08-10 18:31 ` William Morgan
2008-08-10 19:43 ` Nicolas Pouillard
2008-08-10 20:36 ` Marcus Williams
2008-08-13 3:15 ` William Morgan [this message]
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=1218597311-sup-7061@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