From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: gnus sync
Date: Thu, 14 Jul 2011 08:24:36 +0200 [thread overview]
Message-ID: <87mxghgz17.fsf@dod.no> (raw)
In-Reply-To: <87zkkmkk5i.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
[snip!]
> If you GET a server, eg.
> https://myserver/gnussync/backends/nntp/news.gmane.org
> you will get a list with two members "parameters" and "groups"
> I haven't given much thought to the behaviour of
> https://myserver/gnussync/backends/nntp/news.gmane.org/parameters
[snip!]
> If you GET a group, you will get a lisp, or JSON list containing two
> members: "parameters" and "marks".
> I haven't given much thought to the behaviours of group parameters, like
> eg.
> https://myserver/gnussync/backends/nntp/news.gmane.org/groups/gmane.emacs.gnus.general/parameters
[snip!]
When I think about it, and as was discussed in a recent thread, the
contents here, is something I really would prefer to see managed by a
VCS (like my .emacs and .gnus.el files are...).
On the other hand, one of the "cloud(y) gnus" requirements, was that
distributing everything gnus to a priestine gnus should "just work".
And that would definitely include the server and group parameters into
what should be synced...
hm...
next prev parent reply other threads:[~2011-07-14 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 12:07 Richard Riley
2011-06-30 14:38 ` Ted Zlatanov
2011-07-01 7:22 ` Steinar Bang
2011-07-01 12:58 ` Ted Zlatanov
2011-07-10 19:31 ` Steinar Bang
2011-07-14 6:24 ` Steinar Bang [this message]
2011-07-14 7:47 ` Steinar Bang
2011-07-14 7:39 ` Steinar Bang
2011-07-30 21:03 ` Steinar Bang
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=87mxghgz17.fsf@dod.no \
--to=sb@dod.no \
--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).