From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rich Felker <dalias@libc.org>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux-sh list <linux-sh@vger.kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: [PATCH 2/5 v3] sh: add git tree to MAINTAINERS
Date: Mon, 1 Nov 2021 15:10:21 -0400 [thread overview]
Message-ID: <20211101191021.h674kgeuqi4qyhdu@meerkat.local> (raw)
In-Reply-To: <CAMuHMdUw=6RMF4gEhROMBwQALNmmKJgiKQLYymV4m75EZV+DJQ@mail.gmail.com>
On Thu, Oct 28, 2021 at 03:37:47PM +0200, Geert Uytterhoeven wrote:
> > > > I'm omitting this for now since (as noted on the cgit description)
> > > > this server is not provisioned adequately for cloning from scratch,
> > > > and should only be used for fetch into an already-populated mainline
> > > > repo clone. If that's a problem I can see about getting it moved
> > > > somewhere more appropriate.
> > >
> > > Perhaps you can move it to kernel.org?
> >
> > I would love to. This was my hope years ago, but I got bogged down in
> > the GPG key signing requirements and folks not following through with
> > signing my key. Has any of that been streamlined since?
>
> I'll let Konstantin respond...
We still require a valid web of trust before we can issue an account, so
things haven't really changed in that regard. You have to get a PGP signature
from at least 2 other people who already have an account on kernel.org.
If you just need to host your git tree for hosting and sending pull requests,
then there's really no lack of options. Any large commercial git forge will
do just fine, including github, gitlab, gitea, sourcehut, etc. There's nothing
really special about kernel.org in this regard.
-K
next prev parent reply other threads:[~2021-11-01 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 0:19 [PATCH 0/5 v3] sh: fixes for various build and kconfig warnings Randy Dunlap
2021-10-05 0:19 ` [PATCH 1/5 v3] sh: fix kconfig unmet dependency warning for FRAME_POINTER Randy Dunlap
2021-10-05 0:19 ` [PATCH 2/5 v3] sh: add git tree to MAINTAINERS Randy Dunlap
2021-10-05 7:21 ` Geert Uytterhoeven
2021-10-27 20:54 ` Rich Felker
2021-10-28 8:33 ` Geert Uytterhoeven
2021-10-28 13:30 ` Rich Felker
2021-10-28 13:37 ` Geert Uytterhoeven
2021-11-01 19:10 ` Konstantin Ryabitsev [this message]
2021-10-05 0:19 ` [PATCH 3/5 v3] sh: math-emu: drop unused functions Randy Dunlap
2021-10-05 7:26 ` Geert Uytterhoeven
2021-10-06 1:06 ` Randy Dunlap
2021-10-05 0:19 ` [PATCH 4/5 v3] sh: define __BIG_ENDIAN for math-emu Randy Dunlap
2021-10-05 0:19 ` [PATCH 5/5 v3] sh: fix READ/WRITE redefinition warnings Randy Dunlap
2021-10-08 18:39 ` Rob Landley
2021-10-08 19:46 ` Randy Dunlap
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=20211101191021.h674kgeuqi4qyhdu@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=ysato@users.sourceforge.jp \
/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).