Lines Matching full:mail
117 by mail to a maintainer and a public mailing list.
611 by mail to a maintainer and a public mailing list.*
672 Mail: A. Some Human <shuman@example.com>
680 MAINTAINERS file found in the root of the Linux source tree. 'Mail:' for
695 Linux kernel development is completely driven by mail. Very few subsystems use
699 'Mail:' instead. Those mention the name and the email addresses for the
702 Your report later needs to go by mail to those addresses. Additionally, for all
705 lists when sending your issue report by mail later! Maintainers are busy people
1108 Developers often get quite a lot of mail. They thus often just take a few
1109 seconds to skim a mail before deciding to move on or look closer. Thus: the
1153 the ticket. If you report the issue by mail do not attach them, as that makes
1154 the mail too large; instead do one of these things:
1165 replies to your own mail. Just remember to actually do that once the report
1255 When sending the report by mail, CC the Linux regressions mailing list
1257 tracker, proceed to do so. Once filed, forward the report by mail to the
1272 * If the MAINTAINERS file instructed you to report the issue by mail, do not
1278 a private mail to the maintainers instead.
1280 In both cases make sure to also mail your report to the addresses the
1282 them when sending the report by mail. If you filed it in a bug tracker, forward
1320 to your report: go to your mail applications 'Sent' folder and use 'reply-all'
1321 on your mail with the report. This approach will make sure the public mailing
1323 also keeps the mail thread intact, which among others is really important for
1334 mail that you did that, so everyone else knows you honored the request.
1373 mail you sent as reply to your report (make sure it has all those in the CC
1425 get the ball running somehow. If the report got out by mail, do that in the
1426 first lines of a mail that is a reply to your initial mail (see above) which
1445 mail is shortly after the first pre-release (the 'rc1') of a new Linux kernel
1686 one option left: ask for advice. Do that in a mail you sent to the maintainers