From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: Gnus Own-Cloudy?
Date: Tue, 10 Feb 2015 09:17:25 +0000 [thread overview]
Message-ID: <87twyu6s7u.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87iofawbcb.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 10 Feb 2015 14:05:08 +0800")
On Tuesday, 10 Feb 2015 at 14:05, Eric Abrahamsen wrote:
> I never paid any attention to progress of Cloudy Gnus, or whatever we're
> calling it, but then I got a desktop along with my laptop, and suddenly
> I'm VERY INTERESTED.
>
> Before Cloudy is a reality, have any of you had success simply using
> rsync between two machines?
I use unison to keep 4 systems (two desktops, a laptop and a handheld
computer, all running some version of Linux) in sync. Unison is based
on rsync but is a symmetric synchronisation instead of
one-directional. I hope that makes sense...
I am not sure why you see large unread counts. I do not. You do have
to be quite rigorous in the synchronisation and avoid using gnus on two
systems simultaneously, however.
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.1 + Ma Gnus v0.12 + evil-git-bdeb602
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)
next prev parent reply other threads:[~2015-02-10 9:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 6:05 Eric Abrahamsen
2015-02-10 9:17 ` Eric S Fraga [this message]
2015-02-10 10:20 ` Eric Abrahamsen
2015-02-10 10:48 ` Eric S Fraga
2015-02-10 10:53 ` Eric Abrahamsen
2015-02-10 11:45 ` Eric S Fraga
2015-02-10 15:19 ` Jorge A. Alfaro-Murillo
2015-02-11 2:12 ` Eric Abrahamsen
2015-02-11 11:12 ` Eric S Fraga
2015-02-11 13:48 ` Dan Christensen
2015-02-13 5:26 ` Eric Abrahamsen
2015-02-13 5:52 ` Eric Abrahamsen
2015-02-13 14:57 ` Eric Abrahamsen
2015-02-14 13:48 ` Eric Abrahamsen
2015-02-18 11:12 ` [PATCH] " Eric Abrahamsen
2015-02-10 15:31 ` Jorge A. Alfaro-Murillo
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=87twyu6s7u.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).