From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: synching two copies of my mail archives?
Date: 09 Jan 2001 11:01:02 -0500 [thread overview]
Message-ID: <m3r92c3ebl.fsf@peorth.gweep.net> (raw)
In-Reply-To: <ruou278en7j.fsf@g.wolfram.com>
* Bill White <billw@wolfram.com> on Tue, 09 Jan 2001
| How the heck do I keep these two monster archives in sync?! scp and rdist
| can do that, but it takes a while. Is there anything faster/better?
rsync
--
Rat <ratinox@peorth.gweep.net> \ Warning: pregnant women, the elderly, and
Minion of Nathan - Nathan says Hi! \ children under 10 should avoid prolonged
PGP Key: at a key server near you! \ exposure to Happy Fun Ball.
next prev parent reply other threads:[~2001-01-09 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 15:53 Bill White
2001-01-09 16:01 ` Stainless Steel Rat [this message]
2001-01-09 16:03 ` Alexandre Oliva
2001-01-09 16:05 ` Charles Sebold
2001-01-10 16:48 ` more dialup stuff (Re: synching two copies of my mail archives?) Bill White
2001-01-10 17:13 ` Kai Großjohann
2001-01-10 22:49 ` Hannu Koivisto
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=m3r92c3ebl.fsf@peorth.gweep.net \
--to=ratinox@peorth.gweep.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).