Lines Matching refs:patch
46 In a submitted patch it is acceptable to refrain from changing the
47 indentation of large blocks of code to minimize the size of the patch;
48 the person checking in such a patch should reindent it.
129 When you first distribute a patch it may be suitable to just put forth
130 a rough patch, or even just an idea. But before the end of the
138 - Somewhere, a description of what the patch fixes (often in
147 consider the desirability of the changes if there is a separate patch
150 Include words like "I grant permission to distribute this patch under
151 the terms of the GNU Public License" with your patch. By sending a
152 patch to bug-cvs@gnu.org, you implicitly grant this permission.
154 Submitting a patch to bug-cvs is the way to reach the people who have
158 CVS community. Distribute your patch as widely as desired (mailing
160 information describing what the patch is for. It is neither practical
165 with test cases and documentation. So if a patch becomes sufficiently