Lines Matching full:patch
22 .\" $OpenBSD: patch.1,v 1.27 2014/04/15 06:26:54 jmc Exp $
27 .Nm patch
51 will take a patch file containing any of the four forms of difference
58 is omitted, or is a hyphen, the patch will be read from the standard input.
77 contains more than one patch,
79 will try to apply each of them as if they came from separate patch files.
81 to patch must be determined for each diff listing, and that the garbage before
110 Checks that the patch would apply cleanly, but does not modify anything.
114 to interpret the patch file as a context diff.
144 to interpret the patch file as an
155 Note that a larger fuzz factor increases the odds of a faulty patch.
164 skip patches for which a file to patch cannot be found;
165 patch files even though they have the wrong version for the
167 line in the patch;
195 to interpret the patch file as a normal diff.
206 which controls how pathnames found in the patch file are treated,
208 out the patch.
212 For example, supposing the file name in the patch file was
246 that this patch was created with the old and new files swapped.
257 If the first hunk of a patch fails,
263 If it cannot, the patch will continue to be applied normally.
264 (Note: this method cannot detect a reversed patch if it is a normal diff
287 skip patches for which a file to patch cannot be found (the same as
291 line in the patch;
296 to interpret the patch file as a unified context diff (a unidiff).
336 to print out its revision header and patch level.
365 .Ss Patch Application
378 can detect when the line numbers mentioned in the patch are incorrect,
379 and will attempt to find the correct place to apply each hunk of the patch.
399 cannot find a place to install that hunk of the patch, it will put the hunk
403 input patch was a context diff or a normal diff.
406 in the patch file: they reflect the approximate location patch thinks the
485 If no suitable file was found to patch, the patch file is a context or
507 .Dl | patch -d /usr/src/local/blurfl
509 and patch a file in the blurfl directory directly from the article containing
510 the patch.
537 .Ss Notes For Patch Senders
543 file which is patched to increment the patch level as the first diff in the
544 patch file you send out.
547 line in with the patch, it will not let them apply
554 If you are patching something in a subdirectory, be sure to tell the patch
564 will identify the patch as potentially reversed and offer to reverse the patch.
567 whether they already applied the patch.
593 .Bl -tag -width "$TMPDIR/patch*" -compact
594 .It Pa $TMPDIR/patch*
617 exit status so you do not apply a later patch to a partially patched file.
621 couldn't parse your patch file.
625 indicates that there is unprocessed text in the patch file and that
627 is attempting to intuit whether there is a patch in that text and, if so,
628 what kind of patch it is.
660 Of course, compiling without errors is a pretty good indication that the patch
666 However, the results are guaranteed to be correct only when the patch is
667 applied to exactly the same version of the file that the patch was
673 Check patch mode
686 patch the wrong one, and tell you that it succeeded to boot.
688 If you apply a patch you have already applied,
690 will think it is a reversed patch, and offer to un-apply the patch.