All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org, Omar Sandoval <osandov@osandov.com>
Cc: Omar Sandoval <osandov@fb.com>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH blktests] CONTIRIBUTING, README: transfer maintainer role
Date: Wed, 25 May 2022 11:04:24 +0900	[thread overview]
Message-ID: <20220525020424.14131-1-shinichiro.kawasaki@wdc.com> (raw)

To offload blktests maintenance overhead from Omar, I volunteer to take
the blktests maintainer role. Replace Omar's name and e-mail address in
CONTRIBUTING.md with mine. Also note his original authorship in
README.md.

Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
---
 CONTRIBUTING.md | 4 ++--
 README.md       | 3 ++-
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9bda2c4..fd232b7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,8 +2,8 @@
 
 You can contribute to blktests by opening a pull request to the [blktests
 GitHub repository](https://github.com/osandov/blktests) or by sending patches
-to the <linux-block@vger.kernel.org> mailing list and Omar Sandoval
-<osandov@fb.com>. If sending patches, please generate the patch with `git
+to the <linux-block@vger.kernel.org> mailing list and Shin'ichiro Kawasaki
+<shinichiro.kawasaki@wdc.com>. If sending patches, please generate the patch with `git
 format-patch --subject-prefix="PATCH blktests"`. Consider configuring git to do
 this for you with `git config --local format.subjectPrefix "PATCH blktests"`.
 
diff --git a/README.md b/README.md
index fcf07ff..4a1d73f 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,8 @@
 
 blktests is a test framework for the Linux kernel block layer and storage
 stack. It is inspired by the [xfstests](https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/)
-filesystem testing framework.
+filesystem testing framework. It was originally written by Omar Sandoval
+<osandov@fb.com> and [announced in 2017](https://lore.kernel.org/linux-block/20170512184905.GA15267@vader.DHCP.thefacebook.com/).
 
 ## Getting Started
 
-- 
2.36.1


             reply	other threads:[~2022-05-25  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  2:04 Shin'ichiro Kawasaki [this message]
2022-05-25  8:32 ` [PATCH blktests] CONTIRIBUTING, README: transfer maintainer role Damien Le Moal
2022-05-25 22:13 ` Omar Sandoval

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=20220525020424.14131-1-shinichiro.kawasaki@wdc.com \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=osandov@osandov.com \
    /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.