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 14:51:15 -0500 [thread overview]
Message-ID: <ZV5bs6azAPM2UIMq@farprobe> (raw)
In-Reply-To: <268530.1700676155@warthog.procyon.org.uk>
On Wed, Nov 22, 2023 at 18:02:35 +0000, David Howells 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?
Thanks,
--Ben
next prev parent reply other threads:[~2023-11-22 19:51 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 [this message]
2023-11-22 20:28 ` David Howells
2023-11-23 0:53 ` Ben Boeckel
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=ZV5bs6azAPM2UIMq@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.