From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: Gnus backend for GitHub/GitLab?
Date: Thu, 21 Nov 2019 13:31:49 +0100 [thread overview]
Message-ID: <875zjd4dhm.fsf@gnus.org> (raw)
In-Reply-To: <874kyyhgdn.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Wed, 20 Nov 2019 13:38:44 +0100")
Adam Sjøgren <asjo@koldfront.dk> writes:
> I think this is what Michael Albinus addressed - in an email that seems to
> be stuck in the mailing list flow somewhere - where he wrote:
>
> GET /projects/<id>/issues?scope=all&updated_after=2019-11-19T13:22:55.640Z
>
> <id> is your project id.
>
> Best regards, Michael.
>
> That might be useful?
Yup, that's a good API call for Gnus to use.
> I *am* worried about ending up with yet-another-nnslashdot backend,
> which is so dog slow that it is unusable...
Yeah, that's what I was thinking of, too. At first people are like
"yay, Slashdot in Gnus" and then two days later "oh, the slowness; I'd
rather not ever read Slashdot ever again".
> Alternatively I could build a "gitlab_to_nntpd", but I think the
> integration (especially with changing labels and status by editing
> articles, rather than superseding), would be easier/better if it is a
> backend that Gnus knows that editing directly works for?
Yup.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-11-21 12:31 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 [this message]
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
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=875zjd4dhm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=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).