Home
last modified time | relevance | path

Searched refs:reviewer (Results 1 – 25 of 35) sorted by relevance

12

/openbmc/openbmc-tools/tof-voters/libvoters/subcmd/
H A Danalyze-reviews.py74 reviewer = comment["reviewer"]["username"]
76 if reviewer == author:
81 user = comments_per_user[reviewer]
/openbmc/openbmc-build-scripts/tools/
H A Downers152 def review_js(reviewer: str, state: str) -> str:
155 "reviewer": reviewer,
158 "notify_details": {"TO": {"accounts": [reviewer]}},
/openbmc/openbmc-build-scripts/jenkins/
H A Duserid-validation41 while read -r reviewer ;
47 -d "$reviewer" || true
/openbmc/phosphor-pcie-presence/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/openpower-sbe-interface/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/phosphor-mboxd/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/pyphosphor/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/inarp/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/openpower-inventory-upload/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/openpower-logging/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/phosphor-event/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/boost-dbus/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/google-ipmi-sys/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/libbej/
H A DMAINTAINERS30 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/docs/
H A Dcommunity-membership.md10 … | [OWNERS] file reviewer entry …
68 reviewer in an [OWNERS] file.
71 - Primary reviewer for at least 5 changes to the codebase
81 The following apply to the part of codebase for which one would be a reviewer in
84 - Code reviewer status may be a precondition to accepting large code
109 - Primary reviewer for at least 5 reviews to the codebase
120 The following apply to the part of codebase for which one would be a reviewer in
153 - Primary reviewer for at least 10 substantial changes to the codebase
H A Dmeta-layer-guidelines.md22 maintainer is not a reviewer, thereby defeating most of the purpose of the role
/openbmc/webui-vue/.github/ISSUE_TEMPLATE/
H A Ddesign-review.md15 The Invision prototypes have hot spots allowing the reviewer to step through the
/openbmc/qemu/docs/devel/
H A Dmaintainers.rst59 Becoming a reviewer
68 marks you as a 'designated reviewer' - expected to provide regular
H A Dsubmitting-a-patch.rst362 reviewer, the process will be smoother patches will get merged faster.
462 doing everything the reviewer asked. On the other hand, if someone
526 When reviewing a large series, a reviewer can reply to some of the
535 version, to make it easier to focus a reviewer's attention to your
/openbmc/linux/Documentation/process/
H A D6.Followthrough.rst65 understand what the reviewer is trying to say. If possible, fix the things
66 that the reviewer is asking you to fix. And respond back to the reviewer:
70 reviewers. If you believe that the reviewer has misunderstood your code,
73 your explanations make sense, the reviewer will accept them. Should your
75 agree with the reviewer, take some time to think things over again. It can
H A Dsubmitting-patches.rst50 motivated you to do this work. Convince the reviewer that there is a
70 optimization so that the reviewer can weigh costs against benefits.
74 in plain English for the reviewer to verify that the code is behaving
320 bring about a comment or changelog entry so that the next reviewer better
570 technical issues. Any interested reviewer (who has done the work) can
578 or reviewer, should be added by author to the applicable patches when sending
814 bottom, which provides the reviewer and the CI tools enough information
H A Dmaintainer-netdev.rst305 reviewer. You can start with using ``checkpatch.pl``, perhaps even with
334 Put yourself in the shoes of the reviewer. Each patch is read separately
392 ongoing, unless directly instructed by a reviewer.
H A Dresearcher-guidelines.rst154 Reviewed-by: Reviewer <reviewer@email>
/openbmc/openbmc/
H A DREADME.md94 performed by the reviewer.
/openbmc/linux/Documentation/translations/sp_SP/process/
H A Dresearcher-guidelines.rst134 Reviewed-by: Reviewer <reviewer@email>

12