From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: Keeping multiple imap-and-nntp-based gnusae in sync
Date: Tue, 15 Apr 2003 12:08:34 -0400 [thread overview]
Message-ID: <u8zllyb7ngd.fsf@verizon.net> (raw)
In-Reply-To: <znmsmyub.fsf@asfast.com> (Lloyd Zusman's message of "Mon, 14 Apr 2003 19:41:16 -0400")
I use unison <http://www.cis.upenn.edu/~bcpierce/unison/> to keep
(most of) my home directories in sync. For gnus, I'm pretty sure that
keeping .xemacs/*, .gnus, .newsrc* and .Mail and .News directories in
sync works fine though it may be overkill (I exclude the .News/agent
and its subdirectories to save time, for example).
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2003-04-15 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 23:41 Lloyd Zusman
2003-04-15 7:45 ` Simon Josefsson
2003-04-15 10:30 ` Lloyd Zusman
2003-04-15 16:10 ` Simon Josefsson
2003-04-15 16:08 ` David S Goldberg [this message]
2003-04-17 18:43 ` Kai Großjohann
2003-04-17 18:55 ` Lloyd Zusman
2003-04-17 19:07 ` Ted Zlatanov
2003-04-22 6:56 ` Niklas Morberg
2003-04-22 12:57 ` Kai Großjohann
2003-04-22 13:24 ` Ted Zlatanov
2003-04-22 13:19 ` Ted Zlatanov
2003-04-22 13:31 ` Sean Neakums
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=u8zllyb7ngd.fsf@verizon.net \
--to=david.goldberg6@verizon.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;
as well as URLs for NNTP newsgroup(s).