Lines Matching refs:patches

11 end, maintainers use ``git am`` to apply the patches.
29 for patches and other emails alike. https://useplaintext.email may be useful
33 Email clients that are used for Linux kernel patches should send the
37 Don't send patches with ``format=flowed``.  This can cause unexpected
44 Emailed patches should be in ASCII or UTF-8 encoding only.
51 Copy-and-paste (or cut-and-paste) usually does not work for patches
56 Don't use PGP/GPG signatures in mail that contains patches.
57 This breaks many scripts that read and apply the patches.
61 and successfully apply it with 'patch' before sending patches to Linux
69 patches for the Linux kernel.  These are not meant to be complete
95 Works. Some people use this successfully for patches.
108 Some people use this successfully for patches.
124 Some people use Kmail successfully for patches.
153 patches so do not GPG sign them.  Signing patches that have been inserted
156 If you absolutely must send patches as attachments instead of inlining
161 When saving patches that are sent as inlined text, select the email that
203 You can also generate patches with ``git format-patch`` and then use Mutt
216 using Mutt to send patches through Gmail::
285   The easiest thing to do with Thunderbird and patches is to use extensions
344 Does not work for sending patches.