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: <20211027205431.GX7074@brightrain.aerifal.cx>
Date:   Wed, 27 Oct 2021 16:54:32 -0400
From:   Rich Felker <dalias@...c.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     linux-kernel@...r.kernel.org,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        linux-sh@...r.kernel.org,
        John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Geert Uytterhoeven <geert+renesas@...der.be>
Subject: Re: [PATCH 2/5 v3] sh: add git tree to MAINTAINERS

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>
> Cc: Yoshinori Sato <ysato@...rs.sourceforge.jp>
> Cc: Rich Felker <dalias@...c.org>
> Cc: linux-sh@...r.kernel.org
> Cc: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
> Cc: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
> v3: new patch in this series
> 
>  MAINTAINERS |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- 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.

The rest of this series should appear in next shortly.

Rich