Home
last modified time | relevance | path

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

12

/qemu/scripts/
H A Dget_maintainer.pl22 my $email = 1;
74 # rfc822 email address - preloaded methods go here.
170 'email!' => \$email,
228 $email = 0;
237 my $selections = $email + $scm + $status + $subsystem + $web;
239 die "$P: Missing required option: email, scm, status, subsystem or web\n";
243 if ($email &&
247 die "$P: Please select at least 1 email option\n";
637 foreach my $email (@email_to, @list_to) {
638 $email->[0] = deduplicate_email($email->[0]);
[all …]
/qemu/docs/devel/
H A Dsubmitting-a-patch.rst21 * - Patches contain Signed-off-by: Your Name <author@email>
24 - The project uses an email list based workflow. See :ref:`submitting_your_patches`
32 volume of email, often over one thousand messages in a week. The list is
33 moderated; first-time posts from an email address (whether or not you
154 (which becomes the email subject line) is "subsystem: single line
166 for fixing this bug" (they can go below the ``---`` line in the email so
225 The QEMU project uses a public email based workflow for reviewing and
232 to another list.) ``git send-email`` (`step-by-step setup guide
233 <https://git-send-email.io/>`__ and `hints and tips
234 <https://elixir.bootlin.com/linux/latest/source/Documentation/process/email-clients.rst>`__)
[all …]
H A Dcode-provenance.rst17 Signed-off-by: YOUR NAME <YOUR@EMAIL>
56 It is generally expected that the name and email addresses used in one of the
104 email reply containing a ``Reviewed-by`` tag. Subsystem maintainers who
117 behaviour of the patch in some manner, they should send an email reply
180 ("8rev" "Reviewed-by: YOUR NAME <your@email.addr>" nil 1)
181 ("8ack" "Acked-by: YOUR NAME <your@email.addr>" nil 1)
182 ("8test" "Tested-by: YOUR NAME <your@email.addr>" nil 1)
183 ("8sob" "Signed-off-by: YOUR NAME <your@email.addr>" nil 1)
194 iabbrev 8rev Reviewed-by: YOUR NAME <your@email.addr>
195 iabbrev 8ack Acked-by: YOUR NAME <your@email.addr>
[all …]
H A Dsubmitting-a-pull-request.rst27 if they are only CC'd on one email out of the set).
37 tool <https://github.com/stefanha/patches>`__ to add patches from email
57 the pullreq email should quote a tag which is a GPG-signed tag (as
64 string "not for master" in the cover letter email, and make sure the
H A Dstable-process.rst46 to ``qemu-stable@nongnu.org`` if you use git send-email, which is where
H A Dconflict-resolution.rst27 leadership committee by sending an email to qemu@sfconservancy.org, providing
/qemu/
H A D.mailmap7 # sure multiple email addresses get mapped onto the same author.
11 # Proper Name <commit@email.xx>
12 # <proper@email.xx> <commit@email.xx>
13 # Proper Name <proper@email.xx> <commit@email.xx>
14 # Proper Name <proper@email.xx> Commit Name <commit@email.xx>
53 # git config sendemail.from '"Your Name" <your.email@example.com>'
55 # 'git config user.name', which in turn is sufficient for 'git send-email'
56 # to add an extra From: line in the body of your email that takes
H A DREADME.rst77 format-patch' and/or 'git send-email' to format & send the mail to the
101 requires a working 'git send-email' setup, and by default doesn't
162 main methods being email and IRC:
H A D.patchew.yml21 email:
116 Email generated automatically by Patchew [https://patchew.org/].
/qemu/pc-bios/
H A Dedk2-licenses.txt158 not documented, then submit the code on development email list
180 = Change Description / Commit Message / Patch Email =
189 === Start of sample patch email message ===
200 An extra message for the patch email which will not be considered part
205 === End of sample patch email message ===
207 === Notes for sample patch email ===
209 * The first line of commit message is taken from the email's subject
211 commit message is the email's content until the '---' line.
214 === Definitions for sample patch email ===
234 by their real/legal name and their email address.
[all …]
/qemu/.gitlab-ci.d/
H A Dcheck-dco.py36 print("\nChecking for 'Signed-off-by: NAME <EMAIL>' " +
60 print(" ❌ FAIL: bad email in %s" % line)
81 Signed-off-by: YOUR NAME <EMAIL>
/qemu/scripts/coverity-scan/
H A Drun-coverity-scan50 # COVERITY_EMAIL -- the email address to use for uploads (default:
51 # looks at your git coverity.email or user.email config)
338 COVERITY_EMAIL="$(git config coverity.email)"
341 COVERITY_EMAIL="$(git config user.email)"
453 curl --form token="$COVERITY_TOKEN" --form email="$COVERITY_EMAIL" \
/qemu/contrib/gitdm/
H A Daliases2 # This is the email aliases file, mapping secondary addresses onto a
8 # which are actually email addresses with the message:
H A Dgroup-map-janustech2 # Janus Technologies contributors using non-corporate email
H A Dgroup-map-facebook2 # Some Facebook contributors also occasionally use personal email addresses.
H A Dgroup-map-redhat2 # Red Hat contributors using non-corporate email
H A Ddomain-map4 # This maps email domains to nice easy to read company names
/qemu/docs/system/devices/
H A Dccid.rst90 John Doe:CAC Email Signature Certificate u,u,u
91 John Doe:CAC Email Encryption Certificate u,u,u
/qemu/include/hw/dma/
H A Dxlnx_dpdma.h5 * http://www.greensocs.com/ , email: info@greensocs.com
/qemu/include/hw/display/
H A Ddpcd.h5 * http://www.greensocs.com/ , email: info@greensocs.com
H A Dxlnx_dp.h5 * http://www.greensocs.com/ , email: info@greensocs.com
/qemu/include/hw/misc/
H A Dauxbus.h5 * http://www.greensocs.com/ , email: info@greensocs.com
/qemu/hw/display/
H A Ddpcd.c5 * http://www.greensocs.com/ , email: info@greensocs.com
/qemu/include/hw/virtio/
H A Dvirtio-bus.h5 * http://www.greensocs.com/ , email: info@greensocs.com
/qemu/hw/misc/
H A Dauxbus.c5 * http://www.greensocs.com/ , email: info@greensocs.com

12