From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: info-gnus-english <info-gnus-english@gnu.org>
Subject: Re: Keeping Gnus in sync on two machines
Date: Wed, 03 Feb 2021 17:40:29 +0530 [thread overview]
Message-ID: <m2a6slnyh6.fsf@codeisgreat.org> (raw)
In-Reply-To: <CADoYgq8hZbRKetf4-NNartRCBKGv1RXYOmy=+kK3j=pE-aAcpg@mail.gmail.com> (Bob Newell's message of "Tue, 2 Feb 2021 21:36:08 -1000")
Bob Newell <bobnewell@bobnewell.net> writes:
> I also save .newsrc but your list is the similar to mine otherwise,
> and I sync across 8 devices.
I think your use-case is pretty good stress-test. Thanks for encouraging
me.
> ...
> However one difference might be that I keep no machine-local storage
> of mail/articles. You said you use IMAP and I do the same but
> everything resides on the server.
My ~/Mail directory is from the time when I experimented with nnml and
mail-sources (POP3).
Oh! BTW, I still use nnml for local cron jobs. Any idea, how these are
going to be sync’ed? I guess, if I am careful with the up-sync/down-sync
things then it will be ok; as you have mentioned below.
> I've had no problems at all which is pretty amazing considering the
> number and types of devices I keep in sync using rsync and a cloud
> service (costing about $18 a year and well worth it). The big caveats
> are to only use one device at a time, and to remember to sync! I
> almost always remember to up-sync but sometimes I get impatient and
> forget to down-sync.
Any specific options to rsync that might add to the comfort? Or is it
just okay to ‘rsync <src> <dest>’?
--
Regards,
Pankaj Jangid
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2021-02-03 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 3:49 Pankaj Jangid
2021-02-03 7:36 ` Bob Newell
2021-02-03 12:10 ` Pankaj Jangid [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=m2a6slnyh6.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=bobnewell@bobnewell.net \
--cc=info-gnus-english@gnu.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).