Home
last modified time | relevance | path

Searched full:email (Results 1 – 24 of 24) sorted by relevance

/Zephyr-Core-3.7.0/.github/workflows/
Dmanifest.yml24 git config --global user.email "you@example.com"
Dcoding_guidelines.yml40 git config --global user.email "actions@zephyrproject.org"
Dscripts_tests.yml43 git config --global user.email "actions@zephyrproject.org"
Dhello_world_multiplatform.yaml46 git config --global user.email "actions@zephyrproject.org"
Dcompliance.yml48 git config --global user.email "you@example.com"
Dclang.yaml61 git config --global user.email "bot@zephyrproject.org"
Dtwister.yaml76 git config --global user.email "bot@zephyrproject.org"
184 git config --global user.email "bot@zephyrproject.org"
Dbsim-tests.yaml74 git config --global user.email "bot@zephyrproject.org"
Ddoc-build.yml101 git config --global user.email "actions@zephyrproject.org"
/Zephyr-Core-3.7.0/doc/contribute/
Dguidelines.rst139 Signed-off-by: Your Name <your.email@example.com>
146 - ``your.email@example.com`` with the same email address you are using to
151 See :ref:`git_setup` for instructions on configuring user and email settings
343 variables ``user.name`` to your full name, and ``user.email`` to your
344 email address.
346 For example, if your name is ``Zephyr Developer`` and your email
352 git config --global user.email "z.developer@example.com"
379 Signed-off-by: [Your Full Name] <[your.email@address]>
456 with long URLs, email addresses, etc.
476 Signed-off-by: [Your Full Name] <[your.email@address]>
[all …]
Dexternal.rst202 via email, the board will meet to discuss whether to override the
Dcontributor_expectations.rst195 help on Discord or send an email to the `Zephyr devel mailing list`_.
/Zephyr-Core-3.7.0/doc/project/
Dworking_groups.rst95 the TSC (via TSC email list) that shall cover at least the following:
108 modification, a request is made to the TSC email list.
Dtsc.rst173 - Should there be any objections raised, the vote will move to email, and be
Drelease_process.rst462 #. Send an email to the mailing lists (``announce`` and ``devel``)
498 #. Send an email to the mailing lists (``announce`` and ``devel``) with a link
/Zephyr-Core-3.7.0/doc/develop/api/
Dapi_lifecycle.rst106 #. 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-Core-3.7.0/doc/security/
Dreporting.rst9 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-Core-3.7.0/
DCODE_OF_CONDUCT.md34 * Publishing others' private information, such as a physical or email address,
/Zephyr-Core-3.7.0/scripts/ci/
Dcheck_compliance.py9 from email.utils import parseaddr
1246 error1 = f"{sha}: author email ({author}) needs to match one of " \
1248 error2 = f"{sha}: author email ({author}) does not follow the " \
1249 f"syntax: First Last <email>."
1250 error3 = f"{sha}: author email ({author}) must be a real email " \
/Zephyr-Core-3.7.0/scripts/
Dcheckpatch.pl2689 my $email = $4;
2701 "$ucfirst_sign_off $email";
2709 "$ucfirst_sign_off $email";
2718 "$ucfirst_sign_off $email";
2722 my ($email_name, $email_address, $comment) = parse_email($email);
2726 "Unrecognized email address: '$email'\n" . $herecurr);
2731 # Don't force email to have quotes
2733 if ("$dequoted$comment" ne $email &&
2734 "<$email_address>$comment" ne $email &&
2735 "$suggested_email$comment" ne $email) {
[all …]
/Zephyr-Core-3.7.0/include/zephyr/bluetooth/
Duuid.h2177 * @brief GATT Characteristic Email Address UUID Value
2181 * @brief GATT Characteristic Email Address
/Zephyr-Core-3.7.0/doc/contribute/coding_guidelines/
Dindex.rst55 send email to safety@lists.zephyrproject.org and provide details on reason
/Zephyr-Core-3.7.0/doc/
Dzephyr.doxyfile.in1712 # If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email
/Zephyr-Core-3.7.0/scripts/kconfig/
Dkconfiglib.py543 Send bug reports, suggestions, and questions to ulfalizer a.t Google's email