From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Keeping two (or more) sups in sync
Date: Fri, 26 Oct 2007 20:52:45 -0700 [thread overview]
Message-ID: <1193456972-sup-117@south> (raw)
In-Reply-To: <4718C356.5090105@quintic.co.uk>
Excerpts from Marcus Williams's message of Fri Oct 19 07:46:46 -0700 2007:
> To keep the indexes in sync is it enough to copy the .sup directory
> between the two machines? Or should I be using sup-dump?
If the architectures are the same, copying the .sup directory should
work and is probably the best way of ensuring everything is
synchronized. If the architectures are different, then this becomes a
Ferret question, and I don't really know the answer. Sup-dump should
work in the worst case, but will definitely be slow, and you'll also
have to manually synchronize the other files in .sup/ like sources.yaml,
contacts.txt, etc.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-10-27 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 14:46 Marcus Williams
2007-10-27 3:52 ` 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=1193456972-sup-117@south \
--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