Searched refs:email (Results 1 – 15 of 15) sorted by relevance
/Zephyr-latest/cmake/sca/eclair/ECL/ |
D | out_of_initial_scope.ecl | 1 -doc_begin="Derived from Flavio Ceolin <flavio.ceolin@intel.com> email of July 23rd, 2021."
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 172 Signed-off-by: Your Name <your.email@example.com> 179 - ``your.email@example.com`` with the same email address you are using to 184 See :ref:`git_setup` for instructions on configuring user and email settings 328 variables ``user.name`` to your full name, and ``user.email`` to your 329 email address. 331 For example, if your name is ``Zephyr Developer`` and your email 337 git config --global user.email "z.developer@example.com" 341 …pseudonym or hacker handle. The email address that you use in your Git configuration must match th… 346 ``email address`` and profile ``name`` also match those used in your git configuration 347 (``user.name`` & ``user.email``). [all …]
|
D | external.rst | 202 via email, the board will meet to discuss whether to override the
|
D | contributor_expectations.rst | 254 help on Discord or send an email to the `Zephyr devel mailing list`_.
|
/Zephyr-latest/doc/project/ |
D | working_groups.rst | 95 the TSC (via TSC email list) that shall cover at least the following: 108 modification, a request is made to the TSC email list.
|
D | tsc.rst | 173 - Should there be any objections raised, the vote will move to email, and be
|
D | release_process.rst | 472 #. Send an email to the mailing lists (``announce`` and ``devel``) 517 #. Send an email to the mailing lists (``announce`` and ``devel``) with a link
|
/Zephyr-latest/scripts/west_commands/ |
D | patch.py | 500 "email": cm.commit.author.email or "hidden@github.com", 517 "email": pr.user.email or "hidden@github.com",
|
/Zephyr-latest/scripts/ |
D | checkpatch.pl | 2686 my $email = $4; 2698 "$ucfirst_sign_off $email"; 2706 "$ucfirst_sign_off $email"; 2715 "$ucfirst_sign_off $email"; 2719 my ($email_name, $email_address, $comment) = parse_email($email); 2723 "Unrecognized email address: '$email'\n" . $herecurr); 2730 if ("$dequoted$comment" ne $email && 2731 "<$email_address>$comment" ne $email && 2732 "$suggested_email$comment" ne $email) { 2734 "email address '$email' might be better as '$suggested_email$comment'\n" . $herecurr); [all …]
|
/Zephyr-latest/doc/security/ |
D | reporting.rst | 9 Vulnerabilities to the Zephyr project may be reported via email to the 54 response to an email, the issue shall be transitioned directly to
|
/Zephyr-latest/doc/develop/api/ |
D | api_lifecycle.rst | 106 #. An email must be sent to the ``devel`` mailing list announcing the API 159 #. An email must be sent to the ``devel`` mailing list with a subject identical 197 If the Pull Request is merged then an email must be sent to the ``devel`` and
|
/Zephyr-latest/ |
D | CODE_OF_CONDUCT.md | 34 * Publishing others' private information, such as a physical or email address,
|
/Zephyr-latest/doc/develop/flash_debug/ |
D | host-tools.rst | 514 A valid email address is needed to receive the downloading link.
|
/Zephyr-latest/doc/contribute/coding_guidelines/ |
D | index.rst | 19 send email to safety@lists.zephyrproject.org and provide details on reason
|
/Zephyr-latest/doc/ |
D | zephyr.doxyfile.in | 1795 # If the OBFUSCATE_EMAILS tag is set to YES, Doxygen will obfuscate email
|