From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: where is the gnus-sync documentation?
Date: Tue, 08 Nov 2011 18:44:34 -0600 [thread overview]
Message-ID: <87bosmt98t.fsf@lifelogs.com> (raw)
In-Reply-To: <m2ehxiz65z.fsf@boostpro.com>
On Tue, 08 Nov 2011 15:54:32 -0500 Dave Abrahams <dave@boostpro.com> wrote:
DA> on Sun Nov 06 2011, Steinar Bang <sb-AT-dod.no> wrote:
>>>>>>> Dave Abrahams <dave@boostpro.com>:
>>
>>> I want to understand what this module is for
>>
>> Personally, I use gnus-sync v1 to sync nntp tick marks between three
>> different gnus installations (home desktop, home netbook, and work).
DA> That's what I figured, roughly.
>> But the new version of gnus-sync is capable of more.
DA> what, specifically?
Currently gnus-sync has two modes:
1) file sync: can save arbitrary variables (e.g. the topology), write
everything out every time, very risky
2) LeSync: to CouchDB server, saves in a neutral format, will (I hope)
be supported by other newsreaders as well some day. DB rows are per
group and contain all the marks, the topic, the offset within the topic
(so topics are recreated with all their contents), and the machines
where those groups have been saved. Only the modified groups are saved,
it's very fast and compact JSON.
>>> and how to use it.
>>
>> Ah... that bit is still in the process of being nailed out, I think...?
DA> Even some very rough tutorial/getting started guide would be lovely.
Agreed. I'm not able to produce it now. If you or Steinar could take
what he wrote and the above and put it in a .texi file, it would help.
Or wait for me to get to it--this year, I hope.
Ted
prev parent reply other threads:[~2011-11-09 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 21:22 Dave Abrahams
2011-11-06 22:07 ` Steinar Bang
2011-11-08 20:54 ` Dave Abrahams
2011-11-08 21:53 ` Steinar Bang
2011-11-09 0:44 ` Ted Zlatanov [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=87bosmt98t.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).