All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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: Thu, 28 Oct 2021 09:30:53 -0400	[thread overview]
Message-ID: <20211028133049.GY7074@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMuHMdWUQkhYxXfrG4MG-Ghi62P_XVxkCMb_6qijP-MMgn-JWg@mail.gmail.com>

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

  reply	other threads:[~2021-10-28 13:30 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 [this message]
2021-10-28 13:37         ` Geert Uytterhoeven
2021-11-01 19:10           ` Konstantin Ryabitsev
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=20211028133049.GY7074@brightrain.aerifal.cx \
    --to=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 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.