Lines Matching refs:email

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,
65 Some email client (MUA) hints
129 When composing an email, under options, uncheck "word wrap". The only
130 disadvantage is any text you type in the email will not be word-wrapped
132 way around this is to compose your email with word wrap enabled, then save
137 At the bottom of your email, put the commonly-used patch delimiter before
147 the email if the lines wrap in the composer window. Having word wrapping
150 the email. See: https://bugs.kde.org/show_bug.cgi?id=174034
161 When saving patches that are sent as inlined text, select the email that
163 :menuselection:`save as`.  You can use the whole email unmodified as a patch
237   # Sender, email address, and sign-off line must match