Searched refs:email (Results 1 – 25 of 114) sorted by relevance
12345
| /Linux-v5.4/scripts/ |
| D | get_maintainer.pl | 25 my $email = 1;
233 'email!' => \$email,
305 $email = 0;
314 my $selections = $email + $scm + $status + $subsystem + $web;
320 if ($email &&
930 foreach my $email (@email_to, @list_to) {
931 $email->[0] = deduplicate_email($email->[0]);
935 if ($email &&
940 if ($email && $email_git_blame) {
945 if ($email) {
[all …]
|
| /Linux-v5.4/scripts/package/ |
| D | mkdebian | 107 email=${DEBEMAIL-$EMAIL}
110 if echo $email | grep -q '<.*>'; then
111 maintainer=$email
116 if [ -z "$email" ]; then
118 email="$user@$buildhost"
120 maintainer="$name <$email>"
|
| /Linux-v5.4/Documentation/process/ |
| D | email-clients.rst | 9 These days most developers use ``git send-email`` instead of regular
10 email clients. The man page for this is quite good. On the receiving
21 Patches for the Linux kernel are submitted via email, preferably as
22 inline text in the body of the email. Some maintainers accept
35 Don't let your email client do automatic word wrapping for you.
40 If you configure your email client to send emails with UTF-8 encoding,
60 Some email client (MUA) hints
124 When composing an email, under options, uncheck "word wrap". The only
125 disadvantage is any text you type in the email will not be word-wrapped
127 way around this is to compose your email with word wrap enabled, then save
[all …]
|
| D | embargoed-hardware-issues.rst | 32 The team can be contacted by email at <hardware-security@kernel.org>. This
36 The list is encrypted and email to the list can be sent by either PGP or
116 email has been proven to be the most effective and secure communication
123 email. This initial contact should contain a description of the problem and
169 done via email.
271 of these lists is that email sent to the list is encrypted either with the
273 software decrypts the email and re-encrypts it individually for each
283 the key and S/MIME certificate are conveyed to the subscribers by email
294 by email. The email must be signed with the subscriber's PGP key or S/MIME
301 email from the mailing-list which is signed either with the list's PGP key
[all …]
|
| D | code-of-conduct-interpretation.rst | 89 The Linux kernel community primarily interacts on a set of public email
99 email address, or "official" social media address. Any activity
100 performed using a kernel.org email account must follow the Code of
102 corporate email account must follow the specific rules of that
105 The Code of Conduct does not prohibit continuing to include names, email
|
| D | index.rst | 31 email-clients
|
| D | submitting-patches.rst | 304 into the sign-off area of your patch (note, NOT an email recipient). You
364 See :ref:`Documentation/process/email-clients.rst <email_clients>`
559 email) listed in the From: line of the email header.
680 alphabetically by subject line - pretty much any email reader will
684 The ``subsystem`` in the email's Subject should identify which
687 The ``summary phrase`` in the email's Subject should concisely
688 describe the patch which that email contains. The ``summary
693 Bear in mind that the ``summary phrase`` of your email becomes a
733 then the ``From:`` line from the email header will be used to determine
775 (e.g., when using ``git send-email``) to associate the patch with
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 37 and email that subsystem's maintainer and mailing list. If the subsystem
55 public mailing list(s) in the email thread.
67 a bug in kernel.org bugzilla and send email to
82 It's REALLY important to report bugs that seem unrelated as separate email
101 This is a suggested format for a bug report sent via email or bugzilla.
153 up reports, such as replying to the email thread with "I tried the latest
162 If they don't answer your email, they may be on vacation, or at a Linux
172 report before sending the maintainer a reminder email.
|
| D | ufs.rst | 67 Any ufs bug report you can send to daniel.pirkl@email.cz or
|
| D | security-bugs.rst | 14 The Linux kernel security team can be contacted by email at
71 the email Subject line with "[vs]" as described in the linux-distros wiki:
|
| /Linux-v5.4/Documentation/translations/zh_CN/process/ |
| D | email-clients.rst | 5 :Original: :ref:`Documentation/process/email-clients.rst <email_clients>`
22 现在大多数开发人员使用 ``git send-email`` 而不是常规的电子邮件客户端。这方面
175 # Sender, email address, and sign-off line must match
|
| D | 5.Posting.rst | 153 tag: Full Name <email address> optional-other-stuff
191 :ref:`Documentation/translations/zh_CN/process/email-clients.rst <cn_email_clients>`
|
| D | index.rst | 32 email-clients
|
| /Linux-v5.4/Documentation/translations/it_IT/process/ |
| D | email-clients.rst | 3 :Original: :ref:`Documentation/process/email-clients.rst <email_clients>`
|
| D | index.rst | 33 email-clients
|
| D | howto.rst | 118 - Contenuto delle email
119 - Formato delle email
120 - I destinatari delle email
424 ricevere la stessa email due volte: una dal mittente ed una dalla lista; e non
431 blocchi citati, non scrivete all'inizio dell'email.
465 qualche volta le cose si perdono nell'enorme mucchio di email.
521 interazioni umane. Uno dei benefici dell'uso delle email e di irc come forma
524 che sei è un indirizzo email. Aiuta anche l'aspetto internazionale nel
535 email prima di inviarle in modo da essere certi che abbiano senso in inglese.
549 discarica per le vostre aggiunte. In ogni caso, non inviate 50 email nello
[all …]
|
| /Linux-v5.4/Documentation/translations/ja_JP/ |
| D | howto.rst | 525 email と irc を第一のコミュニケーションの形とする一つの利点は、性別や
527 容します。なぜなら、email アドレスによってのみあなたが認識されるからで
553 しかし、一度に 50 もの email をメーリングリストに送りつけるようなことは
|
| D | stable_kernel_rules.txt | 61 が Linus のツリーに入る時に自動的に stable チームに email される。
|
| /Linux-v5.4/Documentation/translations/zh_CN/ |
| D | SecurityBugs | 30 linux内核安全团队可以通过email<security@kernel.org>来联系。这是
|
| /Linux-v5.4/Documentation/maintainer/ |
| D | configure-git.rst | 22 email = jd@domain.org
|
| D | pull-requests.rst | 16 Original email thread::
74 I will take both what you write in the email pull request _and_ in
77 make it into the pull request email), or you can make the signed
174 inline email to the maintainer and CC LKML and any sub-system specific
|
| /Linux-v5.4/Documentation/networking/device_drivers/intel/ |
| D | ice.rst | 45 with a supported adapter, email the specific information related to the issue
|
| D | igbvf.rst | 64 with a supported adapter, email the specific information related to the issue
|
| /Linux-v5.4/Documentation/networking/device_drivers/pensando/ |
| D | ionic.rst | 43 email::
|
| /Linux-v5.4/Documentation/cpu-freq/ |
| D | index.txt | 42 send an email to linux-pm@vger.kernel.org.
|
12345
