Lines Matching refs:patches

11 end, maintainers use ``git am`` to apply the patches.
28 Email clients that are used for Linux kernel patches should send the
32 Don't send patches with ``format=flowed``.  This can cause unexpected
39 Emailed patches should be in ASCII or UTF-8 encoding only.
46 Copy-and-paste (or cut-and-paste) usually does not work for patches
51 Don't use PGP/GPG signatures in mail that contains patches.
52 This breaks many scripts that read and apply the patches.
56 and successfully apply it with 'patch' before sending patches to Linux
64 patches for the Linux kernel.  These are not meant to be complete
90 Works. Some people use this successfully for patches.
103 Some people use this successfully for patches.
119 Some people use Kmail successfully for patches.
148 patches so do not GPG sign them.  Signing patches that have been inserted
151 If you absolutely must send patches as attachments instead of inlining
156 When saving patches that are sent as inlined text, select the email that
200 You can also generate patches with ``git format-patch`` and then use Mutt
213 using Mutt to send patches through Gmail::
278   The easiest thing to do with Thunderbird and patches is to use an
280   for reading/merging patches into the body text.  To do this, download
316 Does not work for sending patches.