From: Ben Boeckel <me@benboeckel.net>
To: David Howells <dhowells@redhat.com>
Cc: keyrings@vger.kernel.org, Jarkko Sakkinen <jarkko@kernel.org>
Subject: Re: GitLab repo for keyrings
Date: Wed, 22 Nov 2023 19:53:42 -0500 [thread overview]
Message-ID: <ZV6ilnhiE5tQs3RK@farprobe> (raw)
In-Reply-To: <271142.1700684889@warthog.procyon.org.uk>
On Wed, Nov 22, 2023 at 20:28:09 +0000, David Howells wrote:
> Ben Boeckel <me@benboeckel.net> wrote:
>
> > > I'm intending to move keyrings to GitLab for its upstream repo:
> > >
> > > https://gitlab.com/linux-afs/keyutils
> >
> > Thanks for the notice. Is the patch submission workflow going to add
> > merge requests via the GitLab instance? If so, will the list be notified
> > of activity on them?
>
> Hmmm... I wonder if I can make gitlab do that automatically.
I don't see anything on my (unpaid) account at least under project
integrations. Closest that seems useful is a webhook delivery
service…needs something to reflect that to email though. Maybe something
kernel.org would be willing to host (once developed)? For listening to
and categorizing webhooks, we use this project:
https://gitlab.kitware.com/utils/webhook-listen
which turns them into JSON files on disk that can then be used as a work
queue at least. (We split it up because it lets us lifecycle the daemon
handling events independently from the webhook receiver; I recommend
that for email reflection as well.)
Another alternative is setting up a gitlab.com account that receives
notifications and forwards/subscribes using the ML address.
--Ben
next prev parent reply other threads:[~2023-11-23 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 18:02 GitLab repo for keyrings David Howells
2023-11-22 19:51 ` Ben Boeckel
2023-11-22 20:28 ` David Howells
2023-11-23 0:53 ` Ben Boeckel [this message]
2023-12-11 9:39 ` David Howells
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=ZV6ilnhiE5tQs3RK@farprobe \
--to=me@benboeckel.net \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.