| /OK3568_Linux_fs/u-boot/scripts/ |
| H A D | get_maintainer.pl | 25 my $email = 1; 218 'email!' => \$email, 280 $email = 0; 289 my $selections = $email + $scm + $status + $subsystem + $web; 295 if ($email && 745 foreach my $email (@email_to, @list_to) { 746 $email->[0] = deduplicate_email($email->[0]); 750 if ($email && 755 if ($email && $email_git_blame) { 760 if ($email) { [all …]
|
| /OK3568_Linux_fs/kernel/scripts/ |
| H A D | get_maintainer.pl | 26 my $email = 1; 241 'email!' => \$email, 314 $email = 0; 323 my $selections = $email + $scm + $status + $subsystem + $web; 329 if ($email && 954 foreach my $email (@email_to, @list_to) { 955 $email->[0] = deduplicate_email($email->[0]); 959 if ($email && 966 if ($email && $email_git_blame) { 971 if ($email) { [all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/xdg-utils/xdg-utils/ |
| H A D | 1f199813e0eb0246f63b54e9e154970e609575af.patch | 4 Subject: [PATCH] xdg-email: remove attachment handling from mailto 18 scripts/xdg-email.in | 7 +------ 24 diff --git a/scripts/xdg-email.in b/scripts/xdg-email.in 26 --- a/scripts/xdg-email.in 27 +++ b/scripts/xdg-email.in
|
| /OK3568_Linux_fs/yocto/poky/scripts/ |
| H A D | send-error-report | 51 email = input("E-mail (not required): ") 52 return username, email 85 if len(args.email) == 0: 86 args.email = userfile_fp.readline() 96 args.name, args.email = ask_for_contactdetails() 100 userfile_fp.write(args.email.strip() + "\n") 107 jsondata['email'] = args.email.strip()
|
| H A D | send-pull-request | 27 Usage: $(basename $0) [-h] [-a] [-c] [[-t email]...] -p pull-dir 33 -C Add extra CC to each email sent. 35 -t email Explicitly add email to the recipients
|
| /OK3568_Linux_fs/kernel/scripts/package/ |
| H A 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>"
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A 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 28 It's also strongly recommended that you use plain text in your email body, 29 for patches and other emails alike. https://useplaintext.email may be useful 30 for information on how to configure your preferred email client, as well as 31 listing recommended email clients should you not already have a preference. 40 Don't let your email client do automatic word wrapping for you. 45 If you configure your email client to send emails with UTF-8 encoding, [all …]
|
| H A D | embargoed-hardware-issues.rst | 34 The team can be contacted by email at <hardware-security@kernel.org>. This 38 The list is encrypted and email to the list can be sent by either PGP or 121 email has been proven to be the most effective and secure communication 128 email. This initial contact should contain a description of the problem and 174 done via email. 277 of these lists is that email sent to the list is encrypted either with the 279 software decrypts the email and re-encrypts it individually for each 289 the key and S/MIME certificate are conveyed to the subscribers by email 300 by email. The email must be signed with the subscriber's PGP key or S/MIME 307 email from the mailing-list which is signed either with the list's PGP key [all …]
|
| H A D | submitting-patches.rst | 248 into the sign-off area of your patch (note, NOT an email recipient). You 288 easiest way to do this is with ``git send-email``, which is strongly 289 recommended. An interactive tutorial for ``git send-email`` is available at 290 https://git-send-email.io. 292 If you choose not to use ``git send-email``: 308 See :doc:`/process/email-clients` for hints about configuring your e-mail 315 which the patch can be improved, in the form of a reply to your email. You must 327 See :doc:`email-clients` for recommendations on email 353 ``git send-email`` will do this for you automatically. 452 email) listed in the From: line of the email header. [all …]
|
| /OK3568_Linux_fs/u-boot/tools/patman/ |
| H A D | series.py | 118 for email in set(cc_list) - to_set - cc_set: 119 if email == None: 120 email = col.Color(col.YELLOW, "<alias '%s' not found>" 122 if email: 123 print(' Cc: ', email) 135 for email in set(all_ccs) - to_set - cc_set: 136 print(' Cc: ', email)
|
| H A D | settings.py | 204 email = gitutil.GetDefaultUserEmail() 206 if email == None: 207 email = raw_input("Enter email: ") 220 ''' % (name, email), file=f)
|
| H A D | README | 23 git format-patch, git send-email, etc. with the correct parameters 56 file 'doc/git-mailrc' in your U-Boot directory to supply the email aliases 66 user name and email address from the global .gitconfig file. 87 If you want to avoid sending patches to email addresses that are picked up 167 Series-to: email / alias 171 Series-cc: email / alias, ... 199 Cover-letter-cc: email / alias 200 Additional email addresses / aliases to send cover letter to (you 221 Signed-off-by: Their Name <email> 227 Tested-by: Their Name <email> [all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-flask-mail_0.9.1.bb | 1 SUMMARY = "Flask extension for sending email" 2 DESCRIPTION = "A Flask extension for sending email" 3 HOMEPAGE = " https://github.com/rduplain/flask-email"
|
| /OK3568_Linux_fs/yocto/poky/contrib/git-hooks/ |
| H A D | sendemail-validate.sample | 43 email = sys.argv[1] 45 with open(email, "r") as f: 70 with open(email, "w") as f:
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/ruby/ruby/ |
| H A D | 0006-Make-gemspecs-reproducible.patch | 28 s.email = ["mrkn@mrkn.jp"] 41 spec.email = ["aaron@tenderlovemaking.com", "hsbt@ruby-lang.org"] 53 s.email = "nobu@ruby-lang.org" 65 spec.email = ["knu@idaemons.org", "ume@mahoroba.org"]
|
| /OK3568_Linux_fs/yocto/poky/scripts/contrib/ |
| H A D | oe-build-perf-report-email.py | 22 from email.mime.text import MIMEText 70 email = os.environ.get('EMAIL', 72 msg['From'] = "{} <{}>".format(full_name, email)
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A 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.
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | developers.txt | 33 +get-developers+ will return the appropriate +git send-email+ 34 command. If the +-e+ option is passed, only the email addresses are 35 printed in a format suitable for +git send-email --cc-cmd+.
|
| /OK3568_Linux_fs/yocto/poky/documentation/test-manual/ |
| H A D | test-process.rst | 70 box to "generate an email to QA"is also checked. 72 When the build completes, an email is sent out using the send-qa-email 76 Autobuilder which is included in the email. The process from here is 80 - QA teams respond to the email saying which tests they plan to run and
|
| /OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/process/ |
| H A 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
|
| H A 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>`
|
| /OK3568_Linux_fs/buildroot/package/python3/ |
| H A D | 0016-Add-an-option-to-disable-the-curses-module.patch | 28 email email/mime \
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/python/ |
| H A D | python3-setuptools_59.5.0.bb | 26 ${PYTHON_PN}-email \ 51 ${PYTHON_PN}-email \
|
| /OK3568_Linux_fs/yocto/poky/bitbake/contrib/vim/plugin/ |
| H A D | newbb.vim | 11 " Will try to use git to find the user name and email 26 let l:user_email = system("git config --get user.email")
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/tests/auto/qplace/ |
| H A D | tst_qplace.cpp | 387 QPlaceContactDetail email; in contactDetailsTest() local 388 email.setLabel("Email"); in contactDetailsTest() 389 email.setValue("email@email.com"); in contactDetailsTest() 397 place.appendContactDetail(QPlaceContactDetail::Email, email); in contactDetailsTest() 403 QCOMPARE(place.contactDetails(QPlaceContactDetail::Email).at(0), email); in contactDetailsTest() 411 QCOMPARE(place.contactDetails(QPlaceContactDetail::Email).at(0), email); in contactDetailsTest()
|