Lines Matching refs:or
23 unfairly criticizing or belittling the work of any contributor.
59 - Ping the reviewers on Gerrit or on the mailing list. If it is urgent,
80 There are no good or bad review comments. If you have any doubt about a patch or
102 - It complies with the relevant standards or technical documentation (where
129 concerns, questions, or any other type of blocking comment, they should set
175 - The patch aims at complying with any standard or technical documentation
180 should help catch files with incorrect or no copyright/license headers.
182 - There is no third party code or binary blobs with potential IP concerns.
183 Maintainers should look for copyright or license notices in code, and use
201 posted via the commit message or on the mailing list.
209 concerns, questions, or any other type of blocking comment, they should set