diff mbox series

[2/5,v3] sh: add git tree to MAINTAINERS

Message ID 20211005001914.28574-3-rdunlap@infradead.org (mailing list archive)
State New, archived
Headers show
Series sh: fixes for various build and kconfig warnings | expand

Commit Message

Randy Dunlap Oct. 5, 2021, 12:19 a.m. UTC
Add the git tree location for linux-sh.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Rich Felker <dalias@libc.org>
Cc: linux-sh@vger.kernel.org
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
---
v3: new patch in this series

 MAINTAINERS |    1 +
 1 file changed, 1 insertion(+)

Comments

Geert Uytterhoeven Oct. 5, 2021, 7:21 a.m. UTC | #1
On Tue, Oct 5, 2021 at 2:19 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> Add the git tree location for linux-sh.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert
Rich Felker Oct. 27, 2021, 8:54 p.m. UTC | #2
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@infradead.org>
> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> Cc: Rich Felker <dalias@libc.org>
> Cc: linux-sh@vger.kernel.org
> Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> Cc: Geert Uytterhoeven <geert+renesas@glider.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@users.sourcefor
>  M:	Rich Felker <dalias@libc.org>
>  L:	linux-sh@vger.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
Geert Uytterhoeven Oct. 28, 2021, 8:33 a.m. UTC | #3
Hi Rich,

On Wed, Oct 27, 2021 at 10:54 PM Rich Felker <dalias@libc.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@infradead.org>

> > --- linux-next-20211001.orig/MAINTAINERS
> > +++ linux-next-20211001/MAINTAINERS
> > @@ -18047,6 +18047,7 @@ M:    Yoshinori Sato <ysato@users.sourcefor
> >  M:   Rich Felker <dalias@libc.org>
> >  L:   linux-sh@vger.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?

> The rest of this series should appear in next shortly.

Thanks a lot!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Rich Felker Oct. 28, 2021, 1:30 p.m. UTC | #4
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@libc.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@infradead.org>
> 
> > > --- linux-next-20211001.orig/MAINTAINERS
> > > +++ linux-next-20211001/MAINTAINERS
> > > @@ -18047,6 +18047,7 @@ M:    Yoshinori Sato <ysato@users.sourcefor
> > >  M:   Rich Felker <dalias@libc.org>
> > >  L:   linux-sh@vger.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
Geert Uytterhoeven Oct. 28, 2021, 1:37 p.m. UTC | #5
Hi Rich,

CC Konstantin

On Thu, Oct 28, 2021 at 3:30 PM Rich Felker <dalias@libc.org> wrote:
> On Thu, Oct 28, 2021 at 10:33:54AM +0200, Geert Uytterhoeven wrote:
> > On Wed, Oct 27, 2021 at 10:54 PM Rich Felker <dalias@libc.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@infradead.org>
> >
> > > > --- linux-next-20211001.orig/MAINTAINERS
> > > > +++ linux-next-20211001/MAINTAINERS
> > > > @@ -18047,6 +18047,7 @@ M:    Yoshinori Sato <ysato@users.sourcefor
> > > >  M:   Rich Felker <dalias@libc.org>
> > > >  L:   linux-sh@vger.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?

I'll let Konstantin respond...

> > > 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

Good!

> probably go ahead and send a PR?

Actually you're right on time ;-)
Your tree is based on v5.15-rc1, and the merge window for v5.16 is
expected to open on Monday. So you can send the PR right away.

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Konstantin Ryabitsev Nov. 1, 2021, 7:10 p.m. UTC | #6
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
diff mbox series

Patch

--- linux-next-20211001.orig/MAINTAINERS
+++ linux-next-20211001/MAINTAINERS
@@ -18047,6 +18047,7 @@  M:	Yoshinori Sato <ysato@users.sourcefor
 M:	Rich Felker <dalias@libc.org>
 L:	linux-sh@vger.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/