lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Wed,  5 Apr 2023 01:14:06 +0800
From:   Zorro Lang <>
Subject: [RFC PATCH 0/5] fstests specific MAINTAINERS file

I think I might be mad to include that many mailing lists in this patchset...

As I explained in [PATCH 1/5], fstests covers more and more fs testing
thing, so we always get help from fs specific mailing list, due to they
learn about their features and bugs more. Besides that, some folks help
to review patches (relevant with them) more often. So I'd like to bring
in the similar way of linux/MAINTAINERS, records fs relevant mailing lists,
reviewers or supporters (or call co-maintainers). To recognize the
contribution from them, and help more users to know who or what mailing list
can be added in CC list of a patch.

(The MAINTAINERS and are copied from linux project,
then I made some changes for fstests specially.)

PATCH 3~5 are still under reviewing, hasn't been decided...

About [3/5], if someone mailing list doesn't want to be in cc list of related
fstests patch, please clarify, I'll remove.

About [4/5], if someone people doesn't want to be CCed, tell me, I'll remove.

About [5/5], need more reviewing from btrfs list.

If others fs which *always send patches to fstests@* and *hope to have a specific
co-maintainer* who can help more on your patches (to fststs) before merging, refer
to [5/5].


Powered by blists - more mailing lists