From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Rich Felker <dalias@libc.org>
Cc: Rob Landley <rob@coresemi.io>,
Linux-sh list <linux-sh@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Stalled patches for the SH tree
Date: Thu, 29 Jul 2021 10:58:27 +0200 [thread overview]
Message-ID: <3a14d8c5-45e4-84dc-32b9-0bb573ebc77a@physik.fu-berlin.de> (raw)
Hi!
I was wondering whether there is anything I can do to help with the stalled
patches for SH? There have been a number of patches with improvements that
were sent to the list and I think we should pick these up, also not to discourage
external contributors in helping us maintain the SuperH port.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next reply other threads:[~2021-07-29 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 8:58 John Paul Adrian Glaubitz [this message]
2021-07-29 16:11 ` Stalled patches for the SH tree Rob Landley
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=3a14d8c5-45e4-84dc-32b9-0bb573ebc77a@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@coresemi.io \
/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).