From: dick <dick.r.chiang@gmail.com>
To: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Tue, 14 Jan 2020 17:18:35 -0500 [thread overview]
Message-ID: <871rs1smv8.fsf@dick> (raw)
In-Reply-To: <87v9pdu24x.fsf@tullinup.koldfront.dk>
AS> As far as I can see, these need to be mapped to article numbers, so Gnus
AS> can get information about max number and min number for the group, and to
AS> retrieve articles by number.
Yes, absolutely, your backend needs to sequentially number articles (which in
this context are issues/comments).
But that numbering is one of your own making, not gitlab's.
AS> How do you construct a mapping that allows new comments and issues to
AS> arrive, and keeps no state, using only the GitLab API?
I keep an array of articles (to go from our numbering to the issue/comment).
And I maintain a hashtable to go from gitlab's arbitrary id to our numbering.
Is there a requirement to keep no state? I need to at least persist state for
.newsrc.eld to keep track of what has and hasn't been read and seen (yes,
there's a difference in Gnus between "read" and "seen").
next prev parent reply other threads:[~2020-01-14 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 22:11 Adam Sjøgren
2019-11-20 3:31 ` Eric Abrahamsen
2019-11-20 4:12 ` dick.r.chiang
2019-11-20 11:33 ` Lars Ingebrigtsen
2019-11-20 12:38 ` Adam Sjøgren
[not found] ` <87h82ywu6i.fsf@gmx.de>
2019-11-20 15:01 ` Adam Sjøgren
[not found] ` <87h82yvb7r.fsf@gmx.de>
2019-11-20 15:35 ` Adam Sjøgren
2019-11-21 12:31 ` Lars Ingebrigtsen
2020-01-14 20:42 ` Adam Sjøgren
2020-01-14 21:23 ` dick
2020-01-14 22:03 ` Adam Sjøgren
2020-01-14 22:18 ` dick [this message]
2020-01-14 22:45 ` Adam Sjøgren
2020-01-15 4:47 ` dick
2020-03-17 11:03 ` dick.r.chiang
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=871rs1smv8.fsf@dick \
--to=dick.r.chiang@gmail.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).