linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rich Felker <dalias@libc.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 10:33:54 +0200	[thread overview]
Message-ID: <CAMuHMdWUQkhYxXfrG4MG-Ghi62P_XVxkCMb_6qijP-MMgn-JWg@mail.gmail.com> (raw)
In-Reply-To: <20211027205431.GX7074@brightrain.aerifal.cx>

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

  reply	other threads:[~2021-10-28  8:34 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 [this message]
2021-10-28 13:30       ` Rich Felker
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=CAMuHMdWUQkhYxXfrG4MG-Ghi62P_XVxkCMb_6qijP-MMgn-JWg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=dalias@libc.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).