Lines Matching full:patches

1135 this format is no longer widely used for sending out patches; for that purpose,
2107 .Dq Making Patches ,
2108 for more discussion of making patches for distribution.
3102 detects and warns about common problems like forward patches. It saves any
3103 patches that it could not apply. It can also maintain a
3198 .Ss  Applying Imperfect Patches
3222 .Em  Applying Patches with Changed White Space
3239 .Em  Applying Reversed Patches
3244 To apply such patches, give
3268 anywhere. But most patches add or change lines rather than delete them, so
3384 to print the results of applying patches without actually changing any files.
3473 time instead of UTC. This option is not recommended, because patches using
3503 .Ss  Multiple Patches in a File
3511 .Dq Making Patches ,
3598 .Ss  Applying Patches in Other Directories
3667 .Dq Reversed Patches ) .
3689 to not create backup files, even for mismatched patches; this is the default
3723 makes a new backup file name each time it patches a file. For example, the
3811 The names for reject files (files containing patches that
3824 to place all of the rejected patches in a single file. The
3844 set of patches in a loop, you should check the exit status, so you don't apply
3883 Skip patches that do not contain file names in their headers.
3891 Assume that patches are not reversed even if they look like they are.
3904 Skip patches that do not contain file names in their headers (the same as
3908 Skip patches for which the file has the wrong version for the
3913 Assume that patches are reversed if they look like they are.
3966 .Dq Multiple Patches .
4027 patches containing
4120 .Sh  Tips for Making and Using Patches
4121 Use some common sense when making and using patches. For example, when sending
4122 bug fixes to a program's maintainer, send several small patches, one per independent
4127 patches for updating a software package.
4161 Tell your recipients how to apply the patches. This should include which working
4167 your patches to a copy of the original files.
4173 A patch producer should tell recipients how to apply the patches, so the first
4182 cannot patch such files. If you are having trouble applying such patches,
4217 line. Take care to not send out reversed patches, since these make people
4220 Avoid sending patches that compare backup file names like
4226 into patching a backup file instead of the real file. Instead, send patches
4232 To save people from partially applying a patch before other patches that should
4254 accidentally apply patches in the wrong order.
4256 .Ss  Generating Smaller Patches
4286 patches for files that it depends on, so that the recipients' time stamps
4304 typically needs at least two lines for proper operation when patches do not
5164 .Dq Multiple Patches .
5239 Print the results of applying the patches without actually changing any files.See Section
5251 Remove output files that are empty after the patches have been applied.See Section
5298 Ignore patches that
5302 See Section.Dq Reversed Patches .
5347 .Dq Reversed Patches .
5714 .Lk http://oss.software.ibm.com/developer/opensource/linux/patches/i18n/diffutils-2.7.2-i18n-0.1.pa…
5715 Unfortunately, these patches are incomplete and are to an older version of
5789 to generate a patch that is syntactically correct but patches the wrong files.