linux-kernel - Re: [PATCH 2/5 v3] sh: add git tree to MAINTAINERS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211028133049.GY7074@brightrain.aerifal.cx>
Date:   Thu, 28 Oct 2021 09:30:53 -0400
From:   Rich Felker <dalias@...c.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Linux-sh list <linux-sh@...r.kernel.org>,
        John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Subject: Re: [PATCH 2/5 v3] sh: add git tree to MAINTAINERS

On Thu, Oct 28, 2021 at 10:33:54AM +0200, Geert Uytterhoeven wrote:
> Hi Rich,
> 
> On Wed, Oct 27, 2021 at 10:54 PM Rich Felker <dalias@...c.org> wrote:
> > On Mon, Oct 04, 2021 at 05:19:11PM -0700, Randy Dunlap wrote:
> > > Add the git tree location for linux-sh.
> > >
> > > Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> 
> > > --- linux-next-20211001.orig/MAINTAINERS
> > > +++ linux-next-20211001/MAINTAINERS
> > > @@ -18047,6 +18047,7 @@ M:    Yoshinori Sato <ysato@...rs.sourcefor
> > >  M:   Rich Felker <dalias@...c.org>
> > >  L:   linux-sh@...r.kernel.org
> > >  S:   Maintained
> > > +T:   git git://git.libc.org/linux-sh
> > >  Q:   http://patchwork.kernel.org/project/linux-sh/list/
> > >  F:   Documentation/sh/
> > >  F:   arch/sh/
> >
> > 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?

> > The rest of this series should appear in next shortly.
> 
> Thanks a lot!

Looks like it's been pulled by next now with no reports of anything
going wrong. I know it's late in the release cycle but should I
probably go ahead and send a PR?

Rich