From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
To: qemu-devel@nongnu.org
Cc: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
Subject: [PATCH 0/1] Resolution of sh4 maintainership
Date: Thu, 11 Jun 2020 00:17:42 +0200 [thread overview]
Message-ID: <20200610221743.24627-1-aleksandar.qemu.devel@gmail.com> (raw)
This series consists of a single patch that introduces a new
maintainer for sh4 target.
He may or may not adjust further the details of sh4 sections,
with recent discussions in mind.
The idea is that noone imposes his particular vision on the
new maintainer person, but that we let him organize himself
the way it suites his style, and his code situation, and his
target position.
Three "Acked-by"s were deduced from the content of recent
discussions on the mailing list.
Aleksandar Markovic (1):
MAINTAINERS: Adjust sh4 maintainership
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2020-06-10 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 22:17 Aleksandar Markovic [this message]
2020-06-10 22:17 ` [PATCH 1/1] MAINTAINERS: Adjust sh4 maintainership Aleksandar Markovic
2020-06-10 22:51 ` Philippe Mathieu-Daudé
2020-06-10 23:41 ` Aleksandar Markovic
2020-06-11 8:25 ` Thomas Huth
2020-06-11 9:19 ` Aleksandar Markovic
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=20200610221743.24627-1-aleksandar.qemu.devel@gmail.com \
--to=aleksandar.qemu.devel@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).