diff options
author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2022-03-31 01:31:31 +0200 |
---|---|---|
committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2022-03-31 01:31:31 +0200 |
commit | f7b0a7f4eca54797165e3c08bfb6575d082ced46 (patch) | |
tree | f3171f1873ced07e99d449f7bcbfc10f4b4939df /pcr/xen/patch-ovmf-use-python2.patch | |
parent | a01e9730359ca8ff4886986dffa9f4c3eeb64782 (diff) | |
download | abslibre-f7b0a7f4eca54797165e3c08bfb6575d082ced46.tar.gz abslibre-f7b0a7f4eca54797165e3c08bfb6575d082ced46.tar.bz2 abslibre-f7b0a7f4eca54797165e3c08bfb6575d082ced46.zip |
treewide: Maintainer: GNUtoo: clarify the maintainer situation
The status quo is that any Parabola hacker is expected to (be able to)
modify any packages, and having a single maintainer of a package
discourages that practice as people would typically send a patch to
the maintainer instead of pushing it directly.
So for a start we can add common maintainership on package lacking any
"Maintainer: " header for packages in repositories that are supposed
to be maintained.
As for finding who worked on a given package (in case it could be
needed), the git log should have all the information.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'pcr/xen/patch-ovmf-use-python2.patch')
0 files changed, 0 insertions, 0 deletions