Lines Matching refs:patches

8 end, maintainers use `git am` to apply the patches.
24 Email clients that are used for Linux kernel patches should send the
28 Don't send patches with "format=flowed".  This can cause unexpected
35 Emailed patches should be in ASCII or UTF-8 encoding only.
42 Copy-and-paste (or cut-and-paste) usually does not work for patches
47 Don't use PGP/GPG signatures in mail that contains patches.
48 This breaks many scripts that read and apply the patches.
52 and successfully apply it with 'patch' before sending patches to Linux
59 patches for the Linux kernel.  These are not meant to be complete
82 Works. Some people use this successfully for patches.
93 Some people use this successfully for patches.
109 Some people use Kmail successfully for patches.
137 patches so do not GPG sign them.  Signing patches that have been inserted
140 If you absolutely must send patches as attachments instead of inlining
145 When saving patches that are sent as inlined text, select the email that
215   The easiest thing to do with Thunderbird and patches is to use an
217   for reading/merging patches into the body text.  To do this, download
253 Does not work for sending patches.