Patch (Unix)

patch
A screenshot of using patch
Original author(s)	Larry Wall
Developer(s)	Paul Eggert, Wayne Davison, David MacKenzie, Andreas Grünbacher
Initial release	May 24, 1985; 40 years ago (1985-05-24)
Operating system	Unix and Unix-like, Plan 9, MSX-DOS, Microsoft Windows
Platform	Cross-platform
Type	Command

patch is a shell command that updates text files according to instructions in a separate file, called a patch file. The patch file is a text file that lists the differences between the input file and the desired content. The command is designed to support patch files created via diff. A user creates a patch file by running diff for two versions of a file (original and target) which produces a list of differences that patch can later use to generate the target file from the original file plus the patch file. The term patch is also a verb – meaning to apply a patch.

Developed by a programmer for other programmers, patch was frequently used for updating source code to a newer version. Because of this, many people came to associate patches with source code, whereas patches can in fact be applied to any text. Patched files do not accumulate any unneeded text, which is what some people perceive based on the English meaning of the word; patch is as capable of removing text as it is of adding it.

Patches described here should not be confused with binary patches, which, although can be conceptually similar, are distributed to update binary files comprising the program to a new release.

The original patch program was written by Larry Wall (who went on to create the Perl programming language) and posted to mod.sources^[1] (which later became comp.sources.unix) in May 1985. patch was added to XPG4, which later became POSIX.^[2] Wall's code remains the basis of "patch" programs provided in OpenBSD,^[3] FreeBSD,^[4] and schilytools.^{[5][dubious – discuss]} The Open Software Foundation, which merged into The Open Group, is said to have maintained a derived version.^{[dubious – discuss]} The GNU project/FSF maintains its patch, forked from the Larry Wall version. The repository is different from that of GNU diffutils, but the documentation is managed together.^[6] Originally written for Unix, command has also been ported to Windows (via GnuWin32 and UnxUtils) and many other platforms. An implementation is part of ASCII's MSX-DOS2 Tools for MSX-DOS version 2.^[7]

As patch files are text, they can be used with processes such as quality review and modification via a text editor.

In addition to the diff command, a patch file can be produced by other programs, such as Subversion, CVS, RCS, Mercurial and Git.

Patches have been the crucial component of many source control systems, including CVS.

When more advanced diffs are used, patches can be applied even to files that have been modified in the meantime, as long as those modifications do not interfere with the patch. This is achieved by using "context diffs" and "unified diffs" (also known as "unidiffs"), which surround each change with context, which is the text immediately before and after the changed part. Patch can then use this context to locate the region to be patched even if it has been displaced by changes earlier in the file, using the line numbers in the diffs as a starting point. Because of this property, context and unified diffs are the preferred form of patches for submission to many software projects.

The above features make diff and patch especially popular for exchanging modifications to open-source software. Outsiders can download the latest publicly available source code, make modifications to it, and send them, in diff form, to the development team. Using diffs, the development team has the ability to effectively review the patches before applying them, and can apply them to a newer code base than the one the outside developer had access to.

The following command creates a patch file that encodes how to generated newFile from oldFile and mods.diff. The -u option selects to output in unified diff format.

$ diff -u oldFile newFile > mods.diff

The following command applies the changes to the file identified in mods.diff.

$ patch < mods.diff

Patching a file in a subdirectory requires the additional -pnumber option, where number is 1 if the base directory of the source tree is included in the diff, and 0 otherwise.

A patch can be undone, or reversed, with the '-R' option:

$ patch -R < mods.diff

If the file used as the original is significantly different from the actual original file, the patch cannot be cleanly be applied. For example, if lines of text are inserted at the beginning, the line numbers referred to in the patch will be incorrect. patch is able to recover from this, by looking at nearby lines to relocate the text to be patched. It will also recover when lines of context (for context and unified diffs) are altered; this is described as fuzz.

• Quilt (software)
• rsync
• xdelta
• List of POSIX commands
• IBM Mainframe utility IEBUPDTE a mainframe patch program, created about 20 years earlier (circa ~1964).

The Wikibook Guide to Unix has a page on the topic of: Commands

• GNU Diffutils (includes diff and patch); Documentation
• GNU tools for Win32 – Win32 port of tools, including diff and patch
• Dickey, Thomas E. "DIFFSTAT – make histogram from diff-output". Archived from the original on 2020-01-22. Retrieved 2020-05-01