From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Tue, 14 Jan 2020 23:03:26 +0100 [thread overview]
Message-ID: <87v9pdu24x.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87d0blspf3.fsf@dick>
dick writes:
> It's unimportant how gitlab numbers messages.
I don't understand how it is? At the very least Gnus needs the ids to
get the information about each issue/comment from the API.
> I've written gnus backends whose messages are keyed off non-numeric
> strings.
Do you have any examples online I can look at?
> Gitlab merely needs to provide the parent issue id for each incoming
> child comment. Then I'd write a suitable nngitlab-retrieve-headers
> that spits out the parent id in the `References` header.
How would you map issues and comments to article numbers?
Let's say you have a project team/project as a group team.project. It
has 4 issues with 4, 2, 0 and 1 comments each:
issue 1
comment 1
comment 2
comment 3
comment 4
issue 2
comment 1
comment 2
issue 3
issue 4
comment 1
As far as I can see, these need to be mapped to article numbers, so Gnus
can get information about max number and min number for the group, and
to retrieve articles by number.
How do you construct a mapping that allows new comments and issues to
arrive, and keeps no state, using only the GitLab API?
Best regards,
Adam
--
"6666 - extra evil" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2020-01-14 22:03 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 [this message]
2020-01-14 22:18 ` dick
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=87v9pdu24x.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--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).