History log of /optee_os/scripts/get_maintainer.py (Results 1 – 5 of 5)
Revision Date Author Comments
# 8eb0262b 25-Mar-2022 Jerome Forissier <jerome.forissier@linaro.org>

get_maintainer.py: add OP-TEE mailing list(s) to --release-to

The release annoucements should be sent to the general OP-TEE mailing
list(s), in addition to the maintainers and reviewers. Add the nee

get_maintainer.py: add OP-TEE mailing list(s) to --release-to

The release annoucements should be sent to the general OP-TEE mailing
list(s), in addition to the maintainers and reviewers. Add the needed
bits to extract this information.

Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>

show more ...


# 72ec5fde 20-Feb-2020 Jerome Forissier <jerome@forissier.org>

get_maintainer.py: add --release-to

Adds an option to scripts/get_maintainer.py showing the email addresses
to be used for release announcements. All addresses in Maintainer (M:)
or Reviewer (R:) en

get_maintainer.py: add --release-to

Adds an option to scripts/get_maintainer.py showing the email addresses
to be used for release announcements. All addresses in Maintainer (M:)
or Reviewer (R:) entries are shown.

Signed-off-by: Jerome Forissier <jerome@forissier.org>
Reviewed-by: Joakim Bech <joakim.bech@linaro.org>

show more ...


# 71c9b078 03-Sep-2019 Jerome Forissier <jerome@forissier.org>

get_maintainer.py: fix spelling mistake

OSError is spelled incorrectly, causing the following error:

$ ./scripts/get_maintainer.py core/arch/arm/plat-imx/
Traceback (most recent call last):
Fi

get_maintainer.py: fix spelling mistake

OSError is spelled incorrectly, causing the following error:

$ ./scripts/get_maintainer.py core/arch/arm/plat-imx/
Traceback (most recent call last):
File "./scripts/get_maintainer.py", line 102, in split_patchset
f = open(patchset, "r")
IsADirectoryError: [Errno 21] Is a directory: 'core/arch/arm/plat-imx/'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "./scripts/get_maintainer.py", line 292, in <module>
main()
File "./scripts/get_maintainer.py", line 242, in main
patches = split_patchset(arg)
File "./scripts/get_maintainer.py", line 103, in split_patchset
except OsError:
NameError: name 'OsError' is not defined

Signed-off-by: Jerome Forissier <jerome@forissier.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>

show more ...


# 716f442d 12-Aug-2019 Jerome Forissier <jerome.forissier@linaro.org>

get_maintainer.py: process patches individually

When given the -m/-merge-check option, get_maintainer.py parses the
Acked-by and Reviewed-by tags that may be found in a patchset or
Github PR. In pre

get_maintainer.py: process patches individually

When given the -m/-merge-check option, get_maintainer.py parses the
Acked-by and Reviewed-by tags that may be found in a patchset or
Github PR. In presence of several patches the tags should apply to
each patch individually, not to the whole patchset as is currently
done. As a result, the script may fail to report some unapproved
changes.

Fix this issue by splitting patchsets into individual patches before
processing.

Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: Joakim Bech <joakim.bech@linaro.org>

show more ...


# 28481ff3 09-Aug-2019 Jerome Forissier <jerome.forissier@linaro.org>

Add scripts/get_maintainer.py

Adds a script to help identify all the maintainer/reviewers for some
path in the source tree, or for some patch or Github pull request.
When processing a patch or a pul

Add scripts/get_maintainer.py

Adds a script to help identify all the maintainer/reviewers for some
path in the source tree, or for some patch or Github pull request.
When processing a patch or a pull request the script can take into
account the Acked-by: and Reviewed-by: tags, so that it can easily tell
if a change is ready to be merged or still needs reviewing (and by
whom). Information comes from the MAINTAINERS file.

The script is similar to the Linux kernel's get_maintainer.pl, although
its use cases are a bit different.

Examples:

1. Who maintains the i.MX platform? Do not show the top-level maintainers
(subsystem "THE REST"), unless there is no specific maintainer.

$ ./scripts/get_maintainer.py --strict core/arch/arm/plat-imx
Peng Fan <peng.fan@nxp.com> [@MrVan] (reviewer:NXP (Freescale) i.MX family)
$

2. Who maintains the i.MX configuration file?

$ ./scripts/get_maintainer.py --strict core/arch/arm/plat-imx/conf.mk
Peng Fan <peng.fan@nxp.com> [@MrVan] (reviewer:NXP (Freescale) i.MX family)
Peng Fan <peng.fan@nxp.com> [@MrVan] (reviewer:NXP (Freescale) i.MX7 WaRP7)
Bryan O'Donoghue <bryan.odonoghue@linaro.org> [@bryanodonoghue] (reviewer:NXP (Freescale) i.MX7 WaRP7)
$

3. Is PR 3169 ready for merging?

$ ./scripts/get_maintainer.py --merge-check --github-pr 3169
Downloading https://github.com/OP-TEE/optee_os/pull/3169.patch... Done.
$

4. Is PR 3169 lacking some reviews from subsystem maintainers? In other
words, is it still properly approved for merging if we ignore the tags
given by members of subsystem "THE REST" whenever there is another
subsystem maintainer?

$ ./scripts/get_maintainer.py --merge-check --strict --github-pr 3169
Peng Fan <peng.fan@nxp.com> [@MrVan] (reviewer:NXP (Freescale) i.MX family)
Peng Fan <peng.fan@nxp.com> [@MrVan] (reviewer:NXP (Freescale) i.MX7 WaRP7)
Bryan O'Donoghue <bryan.odonoghue@linaro.org> [@bryanodonoghue] (reviewer:NXP (Freescale) i.MX7 WaRP7)
$

Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Reviewed-by: Joakim Bech <joakim.bech@linaro.org>

show more ...