Lines Matching full:patch
23 .Em patch .
60 .Xr patch
62 .Em patch ,
67 .Xr patch
108 .Xr patch
612 .Xr patch
616 .Xr patch
620 .Xr patch
640 .Xr patch
806 .Xr patch
808 .Xr patch
1241 .Xr patch ,
1383 .Xr patch
1969 .Xr patch
1975 .Dq patch Options .
2097 newer directory, you can make the patch smaller by using the
2105 the patch, write instructions for the user applying the patch to remove the
2106 files that were deleted before applying the patch.See Section
2206 .Xr patch ,
2208 .Xr patch
3084 .Sh Merging with Xr patch
3085 .Xr patch
3090 .Xr patch ,
3093 .Xr patch
3095 .Xr patch
3097 and uses the headers to determine which file to patch. This lets your correspondents
3099 .Xr patch .
3101 .Xr patch
3107 .Xr patch
3109 that specify which file to patch. It applies
3114 .Xr patch
3115 uses heuristics to try to patch the file as well as it can. If no approximate
3117 .Xr patch
3119 .Xr patch
3125 See Section.Dq Invoking patch ,
3127 .Xr patch .
3129 .Ss Selecting the Xr patch Input Format
3130 .Xr patch
3133 format the patch file uses by examining its contents. For patch files that
3136 .Xr patch
3137 to interpret the patch file as a certain format of diff. The output formats
3139 .Xr patch
3163 .Xr patch ,
3164 .Xr patch
3166 control system. Patch currently supports RCS, ClearCase and SCCS. Under RCS
3168 .Xr patch
3179 .Xr patch
3181 .Xr patch
3183 .Xr patch
3189 .Xr patch
3191 .Dq patch and POSIX .
3199 .Xr patch
3200 tries to skip any leading text in the patch file, apply the diff, and then
3202 .Xr patch ,
3205 .Xr patch
3208 .Xr patch
3216 .Xr patch
3225 vice versa. If this happens to a patch file or an input file, the files might
3227 .Xr patch
3233 .Xr patch
3235 sequence of blanks in the patch file matches any nonempty sequence of blanks
3245 .Xr patch
3251 .Xr patch
3256 .Xr patch
3257 can guess that the patch is reversed. If the first hunk of a patch fails,
3258 .Xr patch
3260 .Xr patch
3264 .Xr patch
3265 continues to apply the patch normally. This method cannot detect a reversed
3266 patch if it is a normal diff and the first command is an append (which should
3270 .Xr patch
3273 If you apply a patch that you have already applied,
3274 .Xr patch
3275 thinks it is a reversed patch and offers to un-apply the patch. This could
3277 to un-apply the patch, just answer
3282 .Xr patch
3285 .Em Helping Xr patch Find Inexact Matches
3288 .Xr patch
3289 can detect when the line numbers mentioned in the patch are incorrect, and
3290 it attempts to find the correct place to apply each hunk of the patch. As
3294 .Xr patch
3299 .Xr patch
3303 .Xr patch
3318 factor increases the odds of making a faulty patch. The default fuzz factor
3323 .Xr patch
3324 cannot find a place to install a hunk of the patch, it writes the hunk out
3328 in context format no matter what form the input patch is in. If the input
3332 in the reject file may be different from those in the patch file: they show
3334 .Xr patch
3340 .Xr patch
3343 .Xr patch
3348 .Xr patch
3350 .Xr patch
3354 .Xr patch
3363 that the patch worked, but not a guarantee.
3365 A patch against an empty file applies to a nonexistent file, and vice versa.See Section
3368 .Xr patch
3370 However, the results are guaranteed only when the patch is applied to an exact
3371 copy of the file that the patch was generated from.
3373 .Em Predicting what Xr patch will do
3376 .Xr patch
3377 will do with a complicated or poorly formatted patch. If you are concerned
3379 .Xr patch
3383 .Xr patch
3386 .Xr patch
3387 will modify the files that you expect. If the patch does not do what you want,
3388 you can modify the patch (or the other options to
3389 .Xr patch )
3390 and try another dry run. Once you are satisfied with the proposed patch you
3392 .Xr patch
3409 outputs a patch that adds or deletes the contents of this file. When given
3410 such a patch,
3411 .Xr patch
3414 .Dq patch and POSIX ) ,
3415 .Xr patch
3421 .Xr patch
3422 to remove output files that are empty after applying a patch, even if the
3423 patch does not appear to be one that removed the file.
3425 If the patch appears to create a file that already exists,
3426 .Xr patch
3427 asks for confirmation before applying the patch.
3431 .Xr patch
3434 .Xr patch
3442 .Xr patch
3458 .Xr patch
3482 .Xr patch
3485 of if the file's contents do not exactly match the patch. However, if the
3494 .Xr patch
3504 If the patch file contains more than one patch, and if you do not specify
3506 .Xr patch
3507 tries to apply each patch as if they came from separate patch files. This
3508 means that it determines the name of the file to patch for each patch, and
3509 that it examines the leading text before each patch for file names and prerequisite
3514 .Xr patch
3516 a patch. First,
3517 .Xr patch
3523 .Xr patch
3538 .Xr patch
3540 .Xr patch
3552 .Xr patch
3558 .Xr patch
3563 .Xr patch
3567 .Xr patch
3573 .Xr patch
3574 is not conforming to POSIX, and the patch appears to create a file,
3575 .Xr patch
3580 of the file to patch, and
3581 .Xr patch
3588 .Xr patch
3593 See Section.Dq patch and POSIX ,
3595 .Xr patch
3604 .Xr patch
3607 the current directory for interpreting both file names in the patch file,
3612 For example, while in a mail reading program, you can patch a file in the
3614 directory directly from a message containing the patch like this:
3617 | patch -d /usr/src/emacs
3620 Sometimes the file names given in a patch contain leading directories, but
3621 you keep your files in a directory different from the one given in the patch.
3629 .Xr patch
3633 .Xr patch
3636 For example, suppose the file name in the patch file is
3653 .Xr patch
3661 .Xr patch
3662 creates a backup file if the patch does not exactly match the original input
3664 undo the patch with
3665 .Li patch -R
3669 .Xr patch
3671 .Dq patch and POSIX .
3678 .Xr patch
3679 to make a backup file regardless of whether the patch matches the original
3683 .Xr patch
3688 .Xr patch
3697 .Xr patch
3710 .Xr patch
3719 .Xr patch
3722 .Xr patch
3738 .Xr patch
3778 .Xr patch
3812 .Xr patch
3823 .Xr patch
3832 .Ss Messages and Questions from Xr patch
3833 .Xr patch
3836 .Xr patch
3841 .Xr patch
3845 a later patch to a partially patched file.
3847 .Em Controlling the Verbosity of Xr patch
3850 .Xr patch
3856 .Xr patch
3857 is reading text in the patch file, attempting to determine whether there is
3858 a patch in that text, and if so, what kind of patch it is.
3861 .Xr patch ,
3872 .Xr patch
3878 .Xr patch
3886 Patch files even though they have the wrong version for the
3888 line in the patch;
3910 line in the patch;
3916 .Em Xr patch Quoting Style
3919 .Xr patch
3951 .Xr patch .
3953 .Ss Xr patch and the POSIX Standard
3959 .Xr patch
3984 .Ss GNU Xr patch and Traditional Xr patch
3986 .Xr patch
3988 .Dq patch and POSIX ,
3992 .Xr patch
3995 .Xr patch ,
3997 .Xr patch
4003 .Xr patch ,
4022 .Xr patch
4024 .Xr patch
4033 .Xr patch ,
4041 .Xr patch ,
4043 .Xr patch ,
4051 .Xr patch
4055 .Xr patch .
4059 .Xr patch
4061 of the file to be patched from the patch header. This method did not conform
4063 .Xr patch
4068 line are all identical after prefix-stripping. Your patch is normally compatible
4073 .Xr patch
4079 .Xr patch
4083 .Xr patch
4088 .Xr patch
4091 .Xr patch
4097 .Xr patch ,
4099 .Xr patch ,
4101 .Xr patch
4123 subject, instead of one large, harder-to-digest patch that covers all the
4129 .Ss Tips for Patch Producers
4130 To create a patch that changes an older version of a package into a newer
4136 To generate the patch, use the command
4148 option lets the patch create and remove files;
4150 lets the patch update non-text files;
4154 lets the patch update subdirectories. Here is an example command, using Bourne
4163 .Xr patch
4170 for how to avoid common mistakes when generating a patch.
4172 .Ss Tips for Patch Consumers
4173 A patch producer should tell recipients how to apply the patches, so the first
4174 rule of thumb for a patch consumer is to follow the instructions supplied
4175 with the patch.
4181 .Xr patch
4182 cannot patch such files. If you are having trouble applying such patches,
4184 .Xr patch .
4187 When producing a patch for multiple files, apply
4190 the patch consumer specifies the
4193 file names have different numbers of slashes. For example, do not send a patch
4204 .Xr patch
4218 wonder whether they have already applied the patch.
4225 .Xr patch
4232 To save people from partially applying a patch before other patches that should
4233 have gone before it, you can make the first patch in the patch file update
4238 which contains a patch level or version number. If the input file contains
4240 .Xr patch
4245 line before the patch. If the leading text in the patch file contains a line
4248 .Xr patch
4252 .Xr patch
4257 The simplest way to generate a patch is to use
4260 .Dq Tips for Patch Producers ) ,
4261 but you might be able to reduce the size of the patch by renaming or removing
4262 some files before making the patch. If the older version of the package contains
4269 the patch. Then run those commands yourself in the scratch directory.
4271 If there are any files that you don't need to include in the patch because
4278 exclude them from the patch by giving
4284 If you want your patch to modify a derived file because your recipients lack
4285 tools to build it, make sure that the patch for the derived file follows any
4290 Now you can create the patch using
4294 Add to the top of the patch a note telling the user any
4298 commands to run before applying the patch. Then you can remove the scratch
4301 You can also shrink the patch size by using fewer lines of context, but bear
4303 .Xr patch
4638 .Xr patch
4897 .Xr patch
5125 .Sh Invoking Xr patch
5127 .Xr patch
5131 patch <patchfile
5135 .Xr patch
5139 patch options... [origfile [patchfile]]
5142 You can also specify where to read the patch from with the
5152 .Xr patch
5153 reads the patch (that is, the
5158 .Xr patch
5161 (any text in the patch that comes before the
5167 .Xr patch
5172 .Xr patch
5181 .Ss Options to Xr patch
5183 .Xr patch
5185 .Dq patch and Tradition ,
5187 .Xr patch .
5207 Back up the original contents of each file if the patch does not exactly match
5215 where this option makes a difference, the patch should be generated by
5221 Interpret the patch file as a context diff.See Section
5222 .Dq patch Input .
5228 the current directory for interpreting both file names in the patch file,
5230 .Dq patch Directories .
5244 Interpret the patch file as an
5247 .Dq patch Input .
5258 .Dq patch Messages .
5280 Read the patch from
5283 .Dq patch Options .
5287 Let any sequence of blanks (spaces or tabs) in the patch file match any sequence
5293 Interpret the patch file as a normal diff.See Section
5294 .Dq patch Input .
5299 .Xr patch
5314 .Dq patch Options .
5320 See Section.Dq patch Directories .
5326 .Dq patch and POSIX .
5335 See Section.Dq patch Quoting Style .
5346 Assume that this patch was created with the old and new files swapped.See Section
5353 .Dq patch Messages .
5358 .Dq patch Messages .
5369 Interpret the patch file as a unified diff.See Section
5370 .Dq patch Input .
5383 .Dq patch Messages .
5388 .Xr patch
5665 .Xr patch .
5676 .Ss Suggested Projects for Improving GNU Xr diff and Xr patch
5679 to generate a patch from any pair of directory trees, and given the patch
5681 .Xr patch
5683 trees cannot be expressed using current patch formats; also,
5684 .Xr patch
5714 …://oss.software.ibm.com/developer/opensource/linux/patches/i18n/diffutils-2.7.2-i18n-0.1.patch.gz .
5723 .Xr patch
5731 .Xr patch
5735 to include its entire contents in the patch file. There should also be a way
5737 .Xr patch
5741 .Xr patch
5747 .Xr patch
5765 .Xr patch
5774 .Xr patch
5781 generates a patch that
5782 .Xr patch
5786 .Xr patch ,
5789 to generate a patch that is syntactically correct but patches the wrong files.
5797 .Xr patch
5800 .Xr patch
5803 but sometimes it is useful to generate a patch that works even if the recipient
5804 does not have GNU patch, or does not use these options. One way to do this
5858 .Xr patch
5860 .Mt bug-patch@gnu.org .
5865 have a nontrivial fix for the bug, please send it as well. If you have a patch,
5866 please send it too. It may simplify the maintainer's job if the patch is relative