From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: ding@gnus.org
Subject: Re: synching two copies of my mail archives?
Date: 09 Jan 2001 14:03:36 -0200 [thread overview]
Message-ID: <or4rz8k90n.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: Bill White's message of "09 Jan 2001 09:53:36 -0600"
On Jan 9, 2001, Bill White <billw@wolfram.com> wrote:
> 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?
Andrew Tridge's rsync is the best thing since sliced bread.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-01-09 16:03 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
2001-01-09 16:03 ` Alexandre Oliva [this message]
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=or4rz8k90n.fsf@guarana.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).