Searched refs:email (Results 1 – 25 of 101) sorted by relevance
12345
| /Linux-v4.19/scripts/ |
| D | get_maintainer.pl | 25 my $email = 1;
232 'email!' => \$email,
303 $email = 0;
312 my $selections = $email + $scm + $status + $subsystem + $web;
318 if ($email &&
928 foreach my $email (@email_to, @list_to) {
929 $email->[0] = deduplicate_email($email->[0]);
933 if ($email &&
938 if ($email && $email_git_blame) {
943 if ($email) {
[all …]
|
| /Linux-v4.19/scripts/package/ |
| D | mkdebian | 106 email=${DEBEMAIL-$EMAIL}
109 if echo $email | grep -q '<.*>'; then
110 maintainer=$email
115 if [ -z "$email" ]; then
117 email="$user@$buildhost"
119 maintainer="$name <$email>"
|
| /Linux-v4.19/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 | 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 | 29 email-clients
|
| D | submitting-patches.rst | 302 into the sign-off area of your patch (note, NOT an email recipient). You
362 See :ref:`Documentation/process/email-clients.rst <email_clients>`
648 alphabetically by subject line - pretty much any email reader will
652 The ``subsystem`` in the email's Subject should identify which
655 The ``summary phrase`` in the email's Subject should concisely
656 describe the patch which that email contains. The ``summary
661 Bear in mind that the ``summary phrase`` of your email becomes a
701 then the ``From:`` line from the email header will be used to determine
743 (e.g., when using ``git send-email``) to associate the patch with
744 previous relevant discussion, e.g. to link a bug fix to the email with
[all …]
|
| /Linux-v4.19/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 | security-bugs.rst | 14 The Linux kernel security team can be contacted by email at
59 the email Subject line with "[vs]" as described in the linux-distros wiki:
|
| /Linux-v4.19/Documentation/translations/zh_CN/ |
| D | email-clients.txt | 1 Chinese translated version of Documentation/process/email-clients.rst
11 Documentation/process/email-clients.rst 的中文翻译
|
| D | SecurityBugs | 30 linux内核安全团队可以通过email<security@kernel.org>来联系。这是
|
| /Linux-v4.19/Documentation/translations/ja_JP/ |
| D | howto.rst | 535 email と irc を第一のコミュニケーションの形とする一つの利点は、性別や
537 容します。なぜなら、email アドレスによってのみあなたが認識されるからで
563 しかし、一度に 50 もの email をメーリングリストに送りつけるようなことは
|
| D | stable_kernel_rules.txt | 61 が Linus のツリーに入る時に自動的に stable チームに email される。
|
| /Linux-v4.19/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-v4.19/Documentation/networking/ |
| D | ice.txt | 38 If an issue is identified with the released source code, please email
|
| D | ixgbevf.txt | 51 kernel with a supported adapter, email the specific information related
|
| D | i40evf.txt | 53 kernel with a supported adapter, email the specific information related
|
| D | i40e.txt | 147 information and http://www.open-lldp.org/ or email list
188 kernel with a supported adapter, email the specific information related
|
| D | igbvf.txt | 79 kernel with a supported adapter, email the specific information related
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ufs.txt | 59 Any ufs bug report you can send to daniel.pirkl@email.cz or
|
| /Linux-v4.19/Documentation/cpu-freq/ |
| D | index.txt | 42 send an email to linux-pm@vger.kernel.org.
|
| /Linux-v4.19/drivers/staging/speakup/ |
| D | TODO | 42 not want to subscribe to a mailing list, send your email to all of the
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | kirkwood-b3.dts | 10 * old. Either upgrade, or consider the following email:
|
| /Linux-v4.19/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 45 # [0] http://lkml.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com
|
| /Linux-v4.19/Documentation/serial/ |
| D | rocket.txt | 177 email: support@comtrol.com
182 email: support@comtrol.co.uk
|
12345
