Differences between current version and predecessor to the previous major change of patch(1).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Tuesday, May 31, 2005 9:01:02 am | by JohnMcPherson | |
| Older page: | version 2 | Last edited on Tuesday, June 4, 2002 12:22:28 am | by perry | Revert |
@@ -1,1093 +1,278 @@
-PATCH
-!PATCH
-NAME
-SYNOPSIS
-DESCRIPTION
-OPTIONS
-ENVIRONMENT
-FILES
-SEE ALSO
-NOTES FOR PATCH SENDERS
-DIAGNOSTICS
-CAVEATS
-COMPATIBILITY ISSUES
-BUGS
-COPYING
-AUTHORS
-----
-!!NAME
-
+!!Name
patch - apply a diff file to an original
-!!SYNOPSIS
-
-__patch__ [[''options''] [[''originalfile''
-[[''patchfile'']]
+!!Synopsis
+__patch__ [[''options''] [[''originalfile'' [[''patchfile'']]
but usually just
+__patch -p__ ''num patchfile''
-__patch -p__''num''
-____''patchfile''
-DESCRIPTION
+!!Description
+__patch__ takes a patch file ''patchfile'' containing a difference listing produced by the __diff__ program and applies those
+differences to one or more original files, producing patched versions. Normally the patched versions are put in place of the originals.
+Backups can be made; see the __-b__ or __--backup__ option. The names of the files to be patched are usually taken from the patch file,
+but if there's just one file to be patched it can specified on the command line as ''originalfile''.
-__patch
__ takes a patch file ''patchfile'' containing
-a difference listing produced by the
__diff
__ program and
-applies those differences to one or more original files
,
-producing patched versions. Normally the patched versions
-are put in place of the originals. Backups can be made; see
-the
__-b
__ or __--backup
__ option. The names of the
-files to be patched
are usually taken from
the patch file
,
-but if there's just one file
to be patched it can specified
-on
the command line as ''originalfile''
.
+Upon startup, patch attempts to determine the type of the diff listing, unless overruled by a
__-c
__ (
__--context
__)
, __-e__ (__--
+ed__),
__-n
__ (__--normal__),
or __-u__ (
__--unified
__)
option. Context diffs (old-style, new-style, and unified) and normal diffs
are
+applied by
the __
patch__ program itself
, while __ed__ diffs are simply fed
to the ed(1) editor via a pipe
.
+__patch__ tries to skip any leading garbage, apply the diff, and then skip any trailing garbage. Thus you could feed an article or
+message containing a diff listing to __patch__, and it should work. If the entire diff is indented by a consistent amount, or if a
+context diff contains lines ending in CRLF or is encapsulated one or more times by prepending -__ __-__ __
-Upon startup
, patch attempts to determine
the type
of the
-diff listing, unless overruled by
a __-c
__
-(__--
context__), __-e
__ (__--ed
__)
, __-n
__
-(__--normal__)
, or __-u
__ (
__--unified
__) option.
-Context diffs
(old-style, new-style, and unified) and normal
-diffs are applied by
the __patch
__ program itself
, while
-ed
__ diffs are simply fed to
the ed(1
) editor
-via
a pipe
.
+With context diffs
, and to a lesser extent with normal diffs, __
patch__ can detect when the line numbers mentioned in the patch are incorrect, and
attempts to find
the correct place to apply each hunk
of the patch. As
a first guess, it takes the line number mentioned for the hunk, plus or minus any offset used in applying the previous hunk. If that is not the correct place,
__patch
__ scans both forwards and backwards for a set of lines matching the
context given in the hunk. First
__patch
__ looks for a place where all lines of the context match. If no such place is found, and it's a context diff, and the maximum fuzz factor is set to 1 or more, then another scan takes place ignoring the first and last line of context. If that fails, and the maximum fuzz factor is set to 2 or more, the first two and last two lines of context are ignored, and another scan is made.
(The default maximum fuzz factor is 2.) If
__patch
__ cannot find a place to install that hunk of the patch
, it puts the hunk out to a reject file, which normally is the name of the output file plus a
__.rej
__ suffix
, or __#
__ if
__.rej
__ would generate a file name that is too long
(if even appending
the single character
__#
__ makes the file name too long
, then
__#
__ replaces
the file name's last character
). (The rejected hunk comes out in ordinary context diff form regardless of the input patch's form. If the input was
a normal diff, many of the contexts are simply null.) The line numbers on the hunks in the reject file may be different than in the patch file: they reflect the approximate location patch thinks the failed hunks belong in the new file rather than the old one
.
+As each hunk is completed, you are told if the hunk failed, and if so which line (in the new file) __patch__ thought the hunk should go on. If the hunk is installed at a different line from the line number specified in the diff you are told the offset. A single large offset ''may'' indicate that a hunk was installed in the wrong place. You are also told if a fuzz factor was used to make the match, in which case you should also be slightly suspicious. If the __--verbose__ option is given, you are also told about hunks that match exactly.
-__patch__ tries to skip any
leading garbage, apply
the
-diff, and then skip any trailing garbage. Thus you could
-feed an article or message containing a diff listing
to
-__patch__
, and it should work
. If the entire diff is
-indented by a consistent amount, or if a context diff
-contains lines ending in CRLF or is
-encapsulated one or more times by prepending -__
-__-__
-__
+If no original file ''origfile'' is specified on the command line,
__patch__ tries to figure out from the
leading garbage what the name of
the file
to edit is
, using the following rules
.
+First, __patch__ takes an ordered list of candidate file names as follows:
-With
context diffs, and to a lesser extent with normal
-diffs
, __patch__ can detect when the line numbers
-mentioned in the patch are incorrect, and attempts to find
-the correct place to apply each hunk of the patch. As a
-first guess, it
takes the line number mentioned for the
-hunk, plus or minus any offset used in applying the previous
-hunk. If that is not the correct place, __patch__ scans
-both forwards
and backwards for a set of lines matching the
-context given
in the hunk
. First __patch__ looks for a
-place where all lines of the context match. If no such place
-found, and it's a context diff, and the maximum fuzz
-factor is set to 1 or more, then another scan takes place
-ignoring the first and last line of context. If that fails,
-and the maximum fuzz factor is set to 2 or more, the first
-two and last two lines of context are
ignored, and another
-scan is made. (The default maximum fuzz factor is 2.) If
-__patch__ cannot find a place to install that hunk of the
-patch,
it puts the hunk out
to a reject file, which normally
-is
the name of the output file plus a
__.rej
__ suffix,
or
-#__ if
__.rej__ would generate a file
name that is
-too long (if even appending the single character
__#
__
-makes the file name too long, then __#__ replaces the
-file name's last character). (The rejected hunk comes out in
-ordinary context diff form regardless of the input patch's
-form. If the input was a normal diff, many of the contexts
-are simply null.) The line numbers on the hunks in the
-reject file may be different than in the patch file: they
-reflect the approximate location patch thinks the failed
-hunks belong in the new file rather than the old
-one
.
+If the header is that of a
context diff
, __patch__ takes the old
and new file names
in the header
. A name
is ignored if
it does not have enough slashes
to satisfy
the __-p
__''num''
or __--strip=
__''num'' option
. The
name __/dev/null
__ is also ignored
.
+If there is an __Index:__ line in the leading garbage and if either the old and new names are both absent or if __patch__ is conforming to POSIX , __patch__ takes the name in the __Index:__ line.
-As each hunk is completed
, you
are told if
the hunk failed
,
-and if so which line (in the
new file
) __patch__ thought
-the hunk should go on. If the hunk is installed at a
-different line from the line number specified in the diff
-you are told
the offset. A single large offset ''may''
-indicate
that a hunk was installed
in the wrong place. You
-are also told if a fuzz factor was used to make the match,
-in which case you should also be slightly suspicious. If the
-__--verbose__ option is given, you are also told about
-hunks that match exactly
.
+For the purpose of the following rules
, the candidate file names
are considered to be in
the order (old
, new, index
), regardless of
the order
that they appear
in the header
.
+Then __patch__ selects a file name from the candidate list as follows:
-If no original file ''origfile'' is specified on
the
-command line
, __patch__ tries to figure out from the
-leading garbage what
the name of the file
to edit is
, using
-following rules
.
+If some of
the named files exist
, __patch__ selects
the first
name if conforming
to POSIX
, and
the best name otherwise
.
+If __patch__ is not ignoring RCS , !ClearCase, and SCCS (see the __-g__ ''num'' or __--get=__''num'' option), and no named files exist but an RCS , !ClearCase, or SCCS master is found, __patch__ selects the first named file with an RCS , !ClearCase, or SCCS master.
-First
, __patch__ takes an ordered list of candidate
file
-names as follows:
+If no named files exist, no RCS , !ClearCase, or SCCS master was found, some names are given
, __patch__ is not conforming to POSIX , and the patch appears to create a
file, __patch__ selects the best name requiring the creation of the fewest directories.
+If no file name results from the above heuristics, you are asked for the name of the file to patch, and __patch__ selects that name.
-If
the header is that
of a context diff
, __patch__ takes
-old and new file
names in
the header. A
name is ignored
-if
it does not have enough slashes to satisfy
the
-__-p__''num'' or __--strip=__''num'' option. The
-__/dev/null__ is also ignored
.
+To determine
the ''best''
of a nonempty list of file names
, __patch__ first
takes all
the names with
the fewest path
name components; of those,
it then takes all
the names with the shortest basename; of those, it then takes all the shortest names; finally, it takes the first remaining
name.
+Additionally, if the leading garbage contains a __Prereq:__ line, __patch__ takes the first word from the prerequisites line (normally a version number) and checks the original file to see if that word can be found. If not, __patch__ asks for confirmation before proceeding.
-If there
is an __Index:__ line in the leading garbage and
-if either the old and new names are both absent or if
-__patch__ is conforming
to POSIX
,
-__patch__ takes the name
in the __Index
:__
-line.
+The upshot of all this
is that you should be able
to say
, while
in a news interface, something like
the following
:
+ __| patch -d /usr/src/local/blurfl__
-For the purpose of the following rules, the candidate
file
-names are considered to be
in the order (old, new, index),
-regardless of
the order that they appear in
the
-header
.
+and patch a
file in the __blurfl__ directory directly from
the article containing
the patch
.
+If the patch file contains more than one patch, __patch__ tries to apply each of them as if they came from separate patch files. This means, among other things, that it is assumed that the name of the file to patch must be determined for each diff listing, and that the garbage before each diff listing contains interesting things such as file names and revision level, as mentioned previously.
-Then __patch__ selects a file name from the candidate
-list as follows:
+!!Options
+; __-b__ or __--backup__ : Make backup files. That is, when patching a file, rename or copy the original instead of removing it. When backing up a file that does not exist, an empty, unreadable backup file is created as a placeholder to represent the nonexistent file. See the __-V__ or __--version-control__ option for details about how backup file names are determined.
+; __--backup-if-mismatch__ : Back up a file if the patch does not match the file exactly and if backups are not otherwise requested. This is the default unless __patch__ is conforming to POSIX .
+; __--no-backup-if-mismatch__ : Do not back up a file if the patch does not match the file exactly and if backups are not otherwise requested. This is the default if __patch__ is conforming to POSIX .
+; __-B__ ''pref'' or __--prefix=__''pref'' : Prefix ''pref'' to a file name when generating its simple backup file name. For example, with __-B /junk/__ the simple backup file name for __src/patch/util.c__ is __/junk/src/patch/util.c__.
+; __--binary__ : Read and write all files in binary mode, except for standard output and __/dev/tty__. This option has no effect on POSIX -conforming systems. On systems like DOS where this option makes a difference, the patch should be generated by __diff -a --binary__.
+; __-c__ or __--context__ : Interpret the patch file as a ordinary context diff.
+; __-d__ ''dir'' or __--directory=__''dir'' : Change to the directory ''dir'' immediately, before doing anything else.
+; __-D__ ''define'' or __--ifdef=__''define'' : Use the __#ifdef__ ... __#endif__ construct to mark changes, with ''define'' as the differentiating symbol.
+; __--dry-run__ : Print the results of applying the patches without actually changing any files.
+; __-e__ or __--ed__ : Interpret the patch file as an __ed__ script.
+; __-E__ or __--remove-empty-files__ : Remove output files that are empty after the patches have been applied. Normally this option is unnecessary, since __patch__ can examine the time stamps on the header to determine whether a file should exist after patching. However, if the input is not a context diff or if __patch__ is conforming to POSIX , __patch__ does not remove empty patched files unless this option is given. When __patch__ removes a file, it also attempts to remove any empty ancestor directories.
+; __-f__ or __--force__ : Assume that the user knows exactly what he or she is doing, and do not ask any questions. Skip patches whose headers do not say which file is to be patched; patch files even though they have the wrong version for the __Prereq:__ line in the patch; and assume that patches are not reversed even if they look like they are. This option does not suppress commentary; use __-s__ for that.
+; __-F__ ''num'' or __--fuzz=__''num'' : Set the maximum fuzz factor. This option only applies to diffs that have context, and causes __patch__ to ignore up to that many lines in looking for places to install a hunk. Note that a larger fuzz factor increases the odds of a faulty patch. The default fuzz factor is 2, and it may not be set to more than the number of lines of context in the context diff, ordinarily 3.
+; __-g__ ''num'' or __--get=__''num'' : This option controls __patch__'s actions when a file is under RCS or SCCS control, and does not exist or is read-only and matches the default version, or when a file is under !ClearCase control and does not exist. If ''num'' is positive, __patch__ gets (or checks out) the file from the revision control system; if zero, __patch__ ignores RCS , !ClearCase, and SCCS and does not get the file; and if negative, __patch__ asks the user whether to get the file. The default value of this option is given by the value of the __PATCH_GET__ environment variable if it is set; if not, the default value is zero if __patch__ is conforming to POSIX , negative otherwise.
+; __--help__ : Print a summary of options and exit.
+; __-i__ ''patchfile'' or __--input=__''patchfile'' : Read the patch from ''patchfile''. If ''patchfile'' is __-__, read from standard input, the default.
+; __-l__ or __--ignore-whitespace__ : Match patterns loosely, in case tabs or spaces have been munged in your files. Any sequence of one or more blanks in the patch file matches any sequence in the original file, and sequences of blanks at the ends of lines are ignored. Normal characters must still match exactly. Each line of the context must still match a line in the original file.
+; __-n__ or __--normal__ : Interpret the patch file as a normal diff.
-If some of the named files exist,
__patch
__ selects the
-first name if conforming
to POSIX , and the
-best name otherwise
.
+;
__-N
__ or __--forward__ : Ignore patches that seem
to be reversed or already applied. See also __-R__.
+; __-o__ ''outfile'' or __--output=__''outfile'' : Send output to ''outfile'' instead of patching files in place
.
+; __-p__''num'' or __--strip=__''num'' : Strip the smallest prefix containing ''num'' leading slashes from each file name found in the patch file. A sequence of one or more adjacent slashes is counted as a single slash. This controls how file names found in the patch file are treated, in case you keep your files in a different directory than the person who sent out the patch. For example, supposing the file name in the patch file was %%%
+ __/u/howard/src/blurfl/blurfl.c__ %%%
+setting __-p0__ gives the entire file name unmodified, __-p1__ gives %%%
+ __u/howard/src/blurfl/blurfl.c__ %%%
+without the leading slash, __-p4__ gives %%%
+ __blurfl/blurfl.c__ %%%
+and not specifying __-p__ at all just gives you __blurfl.c__. Whatever you end up with is looked for either in the current directory, or the directory specified by the __-d__ option.
-If __patch__ is not ignoring RCS ,
-!ClearCase, and SCCS (see the
__-g__
-''num'' or __
--get=
__''num'' option), and no named
-files exist but an RCS , !ClearCase, or
-SCCS master is found, __patch__ selects
-first named file with an RCS , !ClearCase
,
-or SCCS master
.
+;
__--posix
__ : Conform more strictly to
the POSIX standard
, as follows
.
+* Take the first existing file from the list (old, new, index) when intuiting file names from diff headers.
+* Do not remove files that are empty after patching.
+* Do not ask whether to get files from RCS, !ClearCase, or SCCS.
+* Require that all options precede the files in the command line.
+* Do not backup files when there is a mismatch.
-If no named files exist, no RCS , !ClearCase,
-or SCCS master was found, some
names are
-given,
__patch
__ is not conforming to
-POSIX , and
the patch appears to create a
-file
, __patch
__ selects the best name requiring
the
-creation
of the fewest directories
.
+; __--quoting-style=__''word'' : Use style ''word'' to quote output
names. The ''word'' should be one of the following: %%%
+__literal
__ Output names as-
is. %%%
+__shell__ Quote names for
the shell if they contain shell metacharacters or would cause ambiguous output. %%%
+__shell-always__ Quote names for the shell
, even if they would normally not require quoting. %%%
+
__c
__ Quote names as for a C language string. %%%
+__escape__ Quote as with __c__ except omit
the surrounding double-quote characters. %%%
+%%%
+You can specify the default value
of the __--quoting-style__ option with the environment variable __QUOTING_STYLE__. If that environment variable is not set, the default value is __shell__
.
+; __-r__ ''rejectfile'' or __--reject-file=__''rejectfile'' : Put rejects into ''rejectfile'' instead of the default __.rej__ file.
-If no file name results from
the above heuristics
, you are
-asked for
the name of the file
to patch, and
__patch__
-selects
that name
.
+; __-R__ or __--reverse__ : Assume that this patch was created with
the old and new files swapped. (Yes
, I'm afraid that does happen occasionally, human nature being what it is.) __patch__ attempts to swap each hunk around before applying it. Rejects come out in
the swapped format. The __-R__ option does not work with __ed__ diff scripts because there is too little information
to reconstruct the reverse operation. %%% If the first hunk of a
patch fails
, __patch__ reverses the hunk to see if it can be applied
that way. If it can, you are asked if you want to have the __-R__ option set. If it can't, the patch continues to be applied normally. (Note: this method cannot detect a reversed patch if it is a normal diff and if the first command is an append (i.e. it should have been a delete) since appends always succeed, due to the fact that a null context matches anywhere. Luckily, most patches add or change lines rather than delete them, so most reversed normal diffs begin with a delete, which fails, triggering the heuristic
.)
+; __-s__ or __--silent__ or __--quiet__ : Work silently, unless an error occurs.
-To determine the ''best'' of a nonempty list of file
-names,
__patch
__ first takes all the
names with
the
-fewest path name components
; of those, it then takes all
the
-names with
the shortest basename; of those, it then takes
-all
the shortest names; finally, it takes
the first
-remaining name
.
+;
__-t
__ or __--batch__ : Suppress questions like __-f__, but make some different assumptions: skip patches whose headers do not contain file
names (
the same as __-f__)
; skip patches for which
the file has
the wrong version for
the __Prereq:__ line in
the patch; and assume that patches are reversed if they look like they are
.
+; __-T__ or __--set-time__ : Set the modification and access times of patched files from time stamps given in context diff headers, assuming that the context diff headers use local time. This option is not recommended, because patches using local time cannot easily be used by people in other time zones, and because local time stamps are ambiguous when local clocks move backwards during daylight-saving time adjustments. Instead of using this option, generate patches with UTC and use the __-Z__ or __--set-utc__ option instead.
-Additionally, if the leading garbage contains a
-Prereq:
__ line,
__patch
__ takes
the first word from
-the prerequisites line (normally
a version number) and
-checks the original file to see if that word can be found.
-If not, __patch__ asks for confirmation before
-proceeding
.
+;
__-u
__ or
__--unified
__ : Interpret
the patch file as
a unified context diff
.
+; __-v__ or __--version__ : Print out __patch__'s revision header and patch level, and exit.
-The upshot of all
this is that you should be able to say
,
-while in a news interface
, something like
the
-following:
+; __-V__ ''method'' or __--version-control=__''method'' : Use ''method'' to determine backup file names.
The method can also be given by the __PATCH_VERSION_CONTROL__ (or, if that's not set, the __VERSION_CONTROL__) environment variable, which is overridden by
this option. The method does not affect whether backup files are made; it affects only the names of any backup files that are made. %%% The value of ''method''
is like the GNU Emacs `version-control' variable; __patch__ also recognizes synonyms
that are more descriptive. The valid values for ''method'' are (unique abbreviations are accepted): %%%
+__existing__ or __nil__ Make numbered backups of files that already have them
, therwise simple backups. This is the default. %%%
+__numbered__ or __t__ Make numbered backups. The numbered backup file name for ''F'' is ''F''__.~__''N''__~__ where ''N'' is the version number. %%%
+__simple__ or __never__ Make simple backups. The __-B__ or __--prefix__
, __-Y__ or __--basename-prefix__, and __-z__ or __--suffix__ options specify
the simple backup file name. If none of these options are given, then a simple backup suffix is used; it is the value of the __SIMPLE_BACKUP_SUFFIX__ environment variable if set, and is __.orig__ otherwise.%%%
+With numbered or simple backups, if the backup file name is too long, the backup suffix __~__ is used instead; if even appending __~__ would make the name too long, then __~__ replaces the last character of the file name.
+; __--verbose__ : Output extra information about the work being done. ; __-x__ ''num'' or __--debug=__''num'' : Set internal debugging flags of interest only to __patch__ patchers.
-__| patch
-d
/usr
/src/local
/blurfl
__
+;
__-Y__ ''pref'' or __--basename-prefix=__''pref'' : Prefix ''pref'' to the basename of a file name when generating its simple backup file name. For example, with __-Y .del
/__ the simple backup file name for __src
/patch/util.c__ is __
src/patch/.del
/util.c
__.
+; __-z__ ''suffix'' or __--suffix=__''suffix'' : Use ''suffix'' as the simple backup suffix. For example, with __-z -__ the simple backup file name for __src/patch/util.c__ is __src/patch/util.c-__. The backup suffix may also be specified by the __SIMPLE_BACKUP_SUFFIX__ environment variable, which is overridden by this option.
-and patch a file
in the __blurfl
__ directory directly
-article containing
the patch.
+; __-Z__ or __--set-utc__ : Set the modification
and access times of patched files from time stamps given
in context diff headers, assuming that the context diff headers use Coordinated Universal Time ( UTC , often known as GMT ). Also see
the __-T
__ or __--set-time__ option. %%% The __-Z__ or __--set-utc__ and __-T__ or __--set-time__ options normally refrain
from setting a file's time if
the file's original time does not match the time given in
the patch header, or if its contents do not match the patch exactly. However, if the __-f__ or __--force__ option is given, the file time is set regardless. %%% Due to the limitations of __diff__ output format, these options cannot update the times of files whose contents have not changed. Also, if you use these options, you should remove (e.g. with __make clean__) all files that depend on the patched files, so that later invocations of __make__ do not get confused by the patched files' times
.
+!!Environment
-If the patch file contains more than one patch,
__patch
__
-tries to apply each of them as if they came from separate
-. This means
, among other things
, that it is
-assumed that
the name of the file to patch must be
-determined for each diff listing, and that the garbage
-before each diff listing contains interesting things such as
-file names and revision level, as mentioned
-previously
.
-!!OPTIONS
+;
__PATCH_GET__ : This specifies whether
__patch__ gets missing or read-only
files from RCS
, !ClearCase
, or SCCS by default; see
the __-g__ or __--get__ option
.
+; __POSIXLY_CORRECT__ : If set, __patch__ conforms more strictly to the POSIX standard by default: see the __--posix__ option.
-__-b
__ or
__--backup
__
+;
__QUOTING
_STYLE
__ : Default value of the
__-
-quoting
-style
__ option.
+; __SIMPLE_BACKUP_SUFFIX__ : Extension to use for simple backup file names instead of __.orig__.
-Make backup files. That is
, when patching a file
, rename or
-copy
the original instead of removing it. When backing up a
-file
that does not exist, an empty, unreadable backup file
-created as a placeholder to represent the nonexistent
-file
. See
the __
-V
__ or
__--version-control__ option
-for details about how backup file names are
-determined
.
+; __TMPDIR__
, __TMP__
, __TEMP__ : Directory to put temporary files in; __patch__ uses
the first environment variable in this list
that is set
. If none are set,
the default is system
-dependent; it is normally
__/tmp
__ on Unix hosts
.
+; __VERSION_CONTROL__ or __PATCH_VERSION_CONTROL__ : Selects version control style; see the __-v__ or __--version-control__ option.
-__--backup-if-mismatch__
+!!Files
+; ''$TMPDIR''__/p__ : temporary files
+; __/dev/tty__ : controlling terminal; used to get answers to questions asked of the user
-Back up a file if the patch does not match the file exactly
-and if backups are not otherwise requested. This is the
-default unless __patch__ is conforming to
-POSIX .
-
-
-__--no-backup-if-mismatch__
-
-
-Do not back up a file if the patch does not match the file
-exactly and if backups are not otherwise requested. This is
-the default if __patch__ is conforming to
-POSIX .
-
-
-__-B__ ''pref'' or
-__--prefix=__''pref''
-
-
-Prefix ''pref'' to a file name when generating its simple
-backup file name. For example, with __-B /junk/__ the
-simple backup file name for __src/patch/util.c__ is
-__/junk/src/patch/util.c__.
-
-
-__--binary__
-
-
-Read and write all files in binary mode, except for standard
-output and __/dev/tty__. This option has no effect on
-POSIX -conforming systems. On systems like
-DOS where this option makes a difference, the
-patch should be generated by __diff -a
---binary__.
-
-
-__-c__ or __--context__
-
-
-Interpret the patch file as a ordinary context
-diff.
-
-
-__-d__ ''dir'' or
-__--directory=__''dir''
-
-
-Change to the directory ''dir'' immediately, before doing
-anything else.
-
-
-__-D__ ''define'' or
-__--ifdef=__''define''
-
-
-Use the __#ifdef__ ... __#endif__ construct to mark
-changes, with ''define'' as the differentiating
-symbol.
-
-
-__--dry-run__
-
-
-Print the results of applying the patches without actually
-changing any files.
-
-
-__-e__ or __--ed__
-
-
-Interpret the patch file as an __ed__
-script.
-
-
-__-E__ or __--remove-empty-files__
-
-
-Remove output files that are empty after the patches have
-been applied. Normally this option is unnecessary, since
-__patch__ can examine the time stamps on the header to
-determine whether a file should exist after patching.
-However, if the input is not a context diff or if
-__patch__ is conforming to POSIX ,
-__patch__ does not remove empty patched files unless this
-option is given. When __patch__ removes a file, it also
-attempts to remove any empty ancestor
-directories.
-
-
-__-f__ or __--force__
-
-
-Assume that the user knows exactly what he or she is doing,
-and do not ask any questions. Skip patches whose headers do
-not say which file is to be patched; patch files even though
-they have the wrong version for the __Prereq:__ line in
-the patch; and assume that patches are not reversed even if
-they look like they are. This option does not suppress
-commentary; use __-s__ for that.
-
-
-__-F__ ''num'' or
-__--fuzz=__''num''
-
-
-Set the maximum fuzz factor. This option only applies to
-diffs that have context, and causes __patch__ to ignore
-up to that many lines in looking for places to install a
-hunk. Note that a larger fuzz factor increases the odds of a
-faulty patch. The default fuzz factor is 2, and it may not
-be set to more than the number of lines of context in the
-context diff, ordinarily 3.
-
-
-__-g__ ''num'' or __--get=__''num''
-
-
-This option controls __patch__'s actions when a file is
-under RCS or SCCS control, and
-does not exist or is read-only and matches the default
-version, or when a file is under !ClearCase control and does
-not exist. If ''num'' is positive, __patch__ gets (or
-checks out) the file from the revision control system; if
-zero, __patch__ ignores RCS , !ClearCase,
-and SCCS and does not get the file; and if
-negative, __patch__ asks the user whether to get the
-file. The default value of this option is given by the value
-of the __PATCH_GET__ environment variable if it is set;
-if not, the default value is zero if __patch__ is
-conforming to POSIX , negative
-otherwise.
-
-
-__--help__
-
-
-Print a summary of options and exit.
-
-
-__-i__ ''patchfile'' or
-__--input=__''patchfile''
-
-
-Read the patch from ''patchfile''. If ''patchfile'' is
-__-__, read from standard input, the
-default.
-
-
-__-l__ or __--ignore-whitespace__
-
-
-Match patterns loosely, in case tabs or spaces have been
-munged in your files. Any sequence of one or more blanks in
-the patch file matches any sequence in the original file,
-and sequences of blanks at the ends of lines are ignored.
-Normal characters must still match exactly. Each line of the
-context must still match a line in the original
-file.
-
-
-__-n__ or __--normal__
-
-
-Interpret the patch file as a normal diff.
-
-
-__-N__ or __--forward__
-
-
-Ignore patches that seem to be reversed or already applied.
-See also __-R__.
-
-
-__-o__ ''outfile'' or
-__--output=__''outfile''
-
-
-Send output to ''outfile'' instead of patching files in
-place.
-
-
-__-p__''num'' or
-__--strip=__''num''
-
-
-Strip the smallest prefix containing ''num'' leading
-slashes from each file name found in the patch file. A
-sequence of one or more adjacent slashes is counted as a
-single slash. This controls how file names found in the
-patch file are treated, in case you keep your files in a
-different directory than the person who sent out the patch.
-For example, supposing the file name in the patch file
-was
-
-
-__/u/howard/src/blurfl/blurfl.c__
-
-
-setting __-p0__ gives the entire file name unmodified,
-__-p1__ gives
-
-
-__u/howard/src/blurfl/blurfl.c__
-
-
-without the leading slash, __-p4__ gives
-
-
-__blurfl/blurfl.c__
-
-
-and not specifying __-p__ at all just gives you
-__blurfl.c__. Whatever you end up with is looked for
-either in the current directory, or the directory specified
-by the __-d__ option.
-
-
-__--posix__
-
-
-Conform more strictly to the POSIX standard,
-as follows.
-
-
-Take the first existing file from the list (old, new, index)
-when intuiting file names from diff headers.
-
-
-Do not remove files that are empty after
-patching.
-
-
-Do not ask whether to get files from RCS ,
-!ClearCase, or SCCS .
-
-
-Require that all options precede the files in the command
-line.
-
-
-Do not backup files when there is a mismatch.
-
-
-__--quoting-style=__''word''
-
-
-Use style ''word'' to quote output names. The ''word''
-should be one of the following:
-
-
-__literal__
-
-
-Output names as-is.
-
-
-__shell__
-
-
-Quote names for the shell if they contain shell
-metacharacters or would cause ambiguous output.
-
-
-__shell-always__
-
-
-Quote names for the shell, even if they would normally not
-require quoting.
-
-
-__c__
-
-
-Quote names as for a C language string.
-
-
-__escape__
-
-
-Quote as with __c__ except omit the surrounding
-double-quote characters.
-
-
-You can specify the default value of the
-__--quoting-style__ option with the environment variable
-__QUOTING_STYLE__. If that environment variable is not
-set, the default value is __shell__.
-
-
-__-r__ ''rejectfile'' or
-__--reject-file=__''rejectfile''
-
-
-Put rejects into ''rejectfile'' instead of the default
-__.rej__ file.
-
-
-__-R__ or __--reverse__
-
-
-Assume that this patch was created with the old and new
-files swapped. (Yes, I'm afraid that does happen
-occasionally, human nature being what it is.) __patch__
-attempts to swap each hunk around before applying it.
-Rejects come out in the swapped format. The __-R__ option
-does not work with __ed__ diff scripts because there is
-too little information to reconstruct the reverse
-operation.
-
-
-If the first hunk of a patch fails, __patch__ reverses
-the hunk to see if it can be applied that way. If it can,
-you are asked if you want to have the __-R__ option set.
-If it can't, the patch continues to be applied normally.
-(Note: this method cannot detect a reversed patch if it is a
-normal diff and if the first command is an append (i.e. it
-should have been a delete) since appends always succeed, due
-to the fact that a null context matches anywhere. Luckily,
-most patches add or change lines rather than delete them, so
-most reversed normal diffs begin with a delete, which fails,
-triggering the heuristic.)
-
-
-__-s__ or __--silent__ or __--quiet__
-
-
-Work silently, unless an error occurs.
-
-
-__-t__ or __--batch__
-
-
-Suppress questions like __-f__, but make some different
-assumptions: skip patches whose headers do not contain file
-names (the same as __-f__); skip patches for which the
-file has the wrong version for the __Prereq:__ line in
-the patch; and assume that patches are reversed if they look
-like they are.
-
-
-__-T__ or __--set-time__
-
-
-Set the modification and access times of patched files from
-time stamps given in context diff headers, assuming that the
-context diff headers use local time. This option is not
-recommended, because patches using local time cannot easily
-be used by people in other time zones, and because local
-time stamps are ambiguous when local clocks move backwards
-during daylight-saving time adjustments. Instead of using
-this option, generate patches with UTC and
-use the __-Z__ or __--set-utc__ option
-instead.
-
-
-__-u__ or __--unified__
-
-
-Interpret the patch file as a unified context
-diff.
-
-
-__-v__ or __--version__
-
-
-Print out __patch__'s revision header and patch level,
-and exit.
-
-
-__-V__ ''method'' or
-__--version-control=__''method''
-
-
-Use ''method'' to determine backup file names. The method
-can also be given by the __PATCH_VERSION_CONTROL__ (or,
-if that's not set, the __VERSION_CONTROL__) environment
-variable, which is overridden by this option. The method
-does not affect whether backup files are made; it affects
-only the names of any backup files that are
-made.
-
-
-The value of ''method'' is like the GNU
-Emacs `version-control' variable; __patch__ also
-recognizes synonyms that are more descriptive. The valid
-values for ''method'' are (unique abbreviations are
-accepted):
-
-
-__existing__ or __nil__
-
-
-Make numbered backups of files that already have them,
-otherwise simple backups. This is the default.
-
-
-__numbered__ or __t__
-
-
-Make numbered backups. The numbered backup file name for
-''F'' is ''F''__.~__''N''__~__ where ''N''
-is the version number.
-
-
-__simple__ or __never__
-
-
-Make simple backups. The __-B__ or __--prefix__,
-__-Y__ or __--basename-prefix__, and __-z__ or
-__--suffix__ options specify the simple backup file name.
-If none of these options are given, then a simple backup
-suffix is used; it is the value of the
-__SIMPLE_BACKUP_SUFFIX__ environment variable if set, and
-is __.orig__ otherwise.
-
-
-With numbered or simple backups, if the backup file name is
-too long, the backup suffix __~__ is used instead; if
-even appending __~__ would make the name too long, then
-__~__ replaces the last character of the file
-name.
-
-
-__--verbose__
-
-
-Output extra information about the work being
-done.
-
-
-__-x__ ''num'' or
-__--debug=__''num''
-
-
-Set internal debugging flags of interest only to
-__patch__ patchers.
-
-
-__-Y__ ''pref'' or
-__--basename-prefix=__''pref''
-
-
-Prefix ''pref'' to the basename of a file name when
-generating its simple backup file name. For example, with
-__-Y .del/__ the simple backup file name for
-__src/patch/util.c__ is
-__src/patch/.del/util.c__.
-
-
-__-z__ ''suffix'' or
-__--suffix=__''suffix''
-
-
-Use ''suffix'' as the simple backup suffix. For example,
-with __-z -__ the simple backup file name for
-__src/patch/util.c__ is __src/patch/util.c-__. The
-backup suffix may also be specified by the
-__SIMPLE_BACKUP_SUFFIX__ environment variable, which is
-overridden by this option.
-
-
-__-Z__ or __--set-utc__
-
-
-Set the modification and access times of patched files from
-time stamps given in context diff headers, assuming that the
-context diff headers use Coordinated Universal Time (
-UTC , often known as GMT ).
-Also see the __-T__ or __--set-time__
-option.
-
-
-The __-Z__ or __--set-utc__ and __-T__ or
-__--set-time__ options normally refrain from setting a
-file's time if the file's original time does not match the
-time given in the patch header, or if its contents do not
-match the patch exactly. However, if the __-f__ or
-__--force__ option is given, the file time is set
-regardless.
-
-
-Due to the limitations of __diff__ output format, these
-options cannot update the times of files whose contents have
-not changed. Also, if you use these options, you should
-remove (e.g. with __make clean__) all files that depend
-on the patched files, so that later invocations of
-__make__ do not get confused by the patched files'
-times.
-!!ENVIRONMENT
-
-
-__PATCH_GET__
-
-
-This specifies whether __patch__ gets missing or
-read-only files from RCS , !ClearCase, or
-SCCS by default; see the __-g__ or
-__--get__ option.
-
-
-__POSIXLY_CORRECT__
-
-
-If set, __patch__ conforms more strictly to the
-POSIX standard by default: see the
-__--posix__ option.
-
-
-__QUOTING_STYLE__
-
-
-Default value of the __--quoting-style__
-option.
-
-
-__SIMPLE_BACKUP_SUFFIX__
-
-
-Extension to use for simple backup file names instead of
-__.orig__.
-
-
-__TMPDIR__, __TMP__, __TEMP__
-
-
-Directory to put temporary files in; __patch__ uses the
-first environment variable in this list that is set. If none
-are set, the default is system-dependent; it is normally
-__/tmp__ on Unix hosts.
-
-
-__VERSION_CONTROL__ or
-__PATCH_VERSION_CONTROL__
-
-
-Selects version control style; see the __-v__ or
-__--version-control__ option.
-!!FILES
-
-
-''$TMPDIR''__/p__
-
-
-temporary files
-
-
-__/dev/tty__
-
-
-controlling terminal; used to get answers to questions asked
-of the user
-!!SEE ALSO
+!!See Also
diff(1), ed(1)
+Marshall T. Rose and Einar A. Stefferud, Proposed Standard for Message Encapsulation, Internet RFC:934
-Marshall T. Rose and Einar A. Stefferud, Proposed Standard
-for Message Encapsulation, Internet RFC 934
-NOTES FOR PATCH SENDERS
-
-
-There are several things you should bear in mind if you are
-going to be sending out patches.
-
-
-Create your patch systematically. A good method is the
-command __diff -Naur__ ''old new'' where ''old''
-and ''new'' identify the old and new directories. The
-names ''old'' and ''new'' should not contain any
-slashes. The __diff__ command's headers should have dates
-and times in Universal Time using traditional Unix format,
-so that patch recipients can use the __-Z__ or
-__--set-utc__ option. Here is an example command, using
-Bourne shell syntax:
-
-
-__LC_ALL=C TZ=UTC0 diff -Naur gcc-2.7
-gcc-2.8__
-
-
-Tell your recipients how to apply the patch by telling them
-which directory to __cd__ to, and which __patch__
-options to use. The option string __-Np1__ is
-recommended. Test your procedure by pretending to be a
-recipient and applying your patch to a copy of the original
-files.
-
-
-You can save people a lot of grief by keeping a
-__patchlevel.h__ file which is patched to increment the
-patch level as the first diff in the patch file you send
-out. If you put a __Prereq:__ line in with the patch, it
-won't let them apply patches out of order without some
-warning.
-
-
-You can create a file by sending out a diff that compares
-__/dev/null__ or an empty file dated the Epoch
-(1970-01-01 00:00:00 UTC ) to the file you
-want to create. This only works if the file you want to
-create doesn't exist already in the target directory.
-Conversely, you can remove a file by sending out a context
-diff that compares the file to be deleted with an empty file
-dated the Epoch. The file will be removed unless
-__patch__ is conforming to POSIX and the
-__-E__ or __--remove-empty-files__ option is not
-given. An easy way to generate patches that create and
-remove files is to use GNU __diff__'s
-__-N__ or __--new-file__ option.
-
-
-If the recipient is supposed to use the __-p__''N''
-option, do not send output that looks like
-this:
-
-
-__diff -Naur v2..29/prog/README prog/README
---- v2..29/prog/README Mon Mar 10 15:13:12 1997
-+++ prog/README Mon Mar 17 14:58:22 1997__
-
-
-because the two file names have different numbers of
-slashes, and different versions of __patch__ interpret
-the file names differently. To avoid confusion, send output
-that looks like this instead:
-
-
-__diff -Naur v2..29/prog/README v2..30/prog/README
---- v2..29/prog/README Mon Mar 10 15:13:12 1997
-+++ v2..30/prog/README Mon Mar 17 14:58:22
-1997__
-
-
-Avoid sending patches that compare backup file names like
-__README.orig__, since this might confuse __patch__
-into patching a backup file instead of the real file.
-Instead, send patches that compare the same base file names
-in different directories, e.g. __old/README__ and
-__new/README__.
-
-
-Take care not to send out reversed patches, since it makes
-people wonder whether they already applied the
-patch.
-
-
-Try not to have your patch modify derived files (e.g. the
-file __configure__ where there is a line __configure:
-configure.in__ in your makefile), since the recipient
-should be able to regenerate the derived files anyway. If
-you must send diffs of derived files, generate the diffs
-using UTC , have the recipients apply the
-patch with the __-Z__ or __--set-utc__ option, and
-have them remove any unpatched files that depend on patched
-files (e.g. with __make clean__).
-
-
-While you may be able to get away with putting 582 diff
-listings into one file, it may be wiser to group related
-patches into separate files in case something goes
-haywire.
-!!DIAGNOSTICS
-
-
-Diagnostics generally indicate that __patch__ couldn't
-parse your patch file.
-
+!!Notes for Patch Senders
-If the __--verbose__ option is given, the message
-__Hmm...__ indicates that there is unprocessed text
in
-the patch file and that __patch__ is attempting
to intuit
-whether there is a patch in that text and, if so, what kind
-of patch it is
.
+There are several things you should bear
in mind if you are going
to be sending out patches
.
+Create your patch systematically. A good method is the command __diff -Naur__ ''old new'' where ''old'' and ''new'' identify the old and new directories. The names ''old'' and ''new'' should not contain any slashes. The __diff__ command's headers should have dates and times in Universal Time using traditional Unix format, so that patch recipients can use the __-Z__ or __--set-utc__ option. Here is an example command, using Bourne shell syntax:
-__patch
__'s exit status is 0 if all hunks are applied
-successfully, 1 if some hunks cannot be applied, and
2 if
-there is more serious trouble
. When applying a set of
-patches in a loop it behooves you to check this exit status
-so you don't apply a later patch to a partially patched
-file
.
-!!CAVEATS
+__LC
_ALL=C TZ=UTC0 diff -Naur gcc-
2.7 gcc-2
.8__
+Tell your recipients how to apply the patch by telling them which directory to __cd__ to, and which __patch__ options to use. The option string __-Np1__ is recommended. Test your procedure by pretending to be a recipient and applying your patch to a copy of the original files.
-Context diffs cannot reliably represent the creation or
-deletion
of empty files, empty directories, or special files
-such as symbolic links
. Nor can they represent changes to
-file metadata like ownership, permissions, or whether one
-a hard link
to another
. If changes like these are
-also required, separate instructions (e.g.
a shell script)
-to accomplish them should accompany
the patch.
+You can save people a lot
of grief by keeping a __patchlevel
.h__
file which
is patched
to increment the patch level as the first diff in the patch file you send out
. If you put
a __Prereq:__ line in with
the patch, it won't let them apply patches out of order without some warning
.
+You can create a file by sending out a diff that compares __/dev/null__ or an empty file dated the Epoch (1970-01-01 00:00:00 UTC ) to the file you want to create. This only works if the file you want to create doesn't exist already in the target directory. Conversely, you can remove a file by sending out a context diff that compares the file to be deleted with an empty file dated the Epoch. The file will be removed unless __patch__ is conforming to POSIX and the __-E__ or __--remove-empty-files__ option is not given. An easy way to generate patches that create and remove files is to use GNU __diff__'s __-N__ or __--new-file__ option.
-__patch__ cannot tell if
the line numbers are off in an
-ed
__ script
, and can detect bad line numbers in a
-normal diff only when it finds a change or deletion. A
-context diff using fuzz factor 3 may have the same problem.
-Until a suitable interactive interface is added, you should
-probably
do a context diff in these cases to see if the
-changes made sense. Of course, compiling without errors is a
-pretty good indication
that the patch worked, but not
-always.
+If the recipient is supposed to use
the __-p
__''N'' option
, do not send output
that looks like this:
+ __diff -Naur v2.0.29/prog/README prog/README
+ --- v2.0.29/prog/README Mon Mar 10 15:13:12 1997
+ +++ prog/README Mon Mar 17 14:58:22 1997__
-__patch__ usually produces
the correct results, even when
-it has to do a lot of guessing
. However
, the results are
-guaranteed to be correct only when the patch is applied to
-exactly the same version of the file
that the patch was
-generated from.
-!!COMPATIBILITY ISSUES
+because the two file names have different numbers of slashes, and different versions of
__patch__ interpret
the file names differently
. To avoid confusion
, send output
that looks like this instead:
+ __diff -Naur v2.0.29/prog/README v2.0.30/prog/README
+ --- v2.0.29/prog/README Mon Mar 10 15:13:12 1997
+ +++ v2.0.30/prog/README Mon Mar 17 14:58:22 1997__
-The POSIX standard specifies behavior that
-differs from __patch__'s traditional behavior. You should
-be aware of these differences if you must interoperate with
-__patch__ versions 2.1 and earlier, which do not conform
-to POSIX .
+Avoid sending patches that compare backup file names like __README.orig__, since this might confuse __patch__ into patching a backup file instead of the real file. Instead, send patches that compare the same base file names in different directories, e.g. __old/README__ and __new/README__.
-In traditional __patch__
, the __-p__ option's operand
-was optional, and a bare __-p__ was equivalent to
-__-p0.__ The __-p__ option now requires an operand,
-and __-p __ is now equivalent to __-p0__. For maximum
-compatibility, use options like __-p0__ and
-__-p1__
.
+Take care not to send out reversed patches
, since it makes people wonder whether they already applied
the patch
.
+Try not to have your patch modify derived files (e.g. the file __configure__ where there is a line __configure: configure.in__ in your makefile), since the recipient should be able to regenerate the derived files anyway. If you must send diffs of derived files, generate the diffs using UTC , have the recipients apply the patch with the __-Z__ or __--set-utc__ option, and have them remove any unpatched files that depend on patched files (e.g. with __make clean__).
-Also, traditional __patch__ simply counted slashes when
-stripping path prefixes; __patch__ now counts pathname
-components. That is, a sequence of
one or more adjacent
-slashes now counts as a single slash. For maximum
-portability
, avoid sending
patches containing __//__
in
-file names
.
+While you may be able to get away with putting 582 diff listings into
one file
, it may be wiser to group related
patches into separate files
in case something goes haywire
.
+!!Diagnostics
-In traditional
__patch__, backups were enabled by
-default. This behavior is now enabled with the __-b__ or
-__--backup__ option
.
+Diagnostics generally indicate that
__patch__ couldn't parse your patch file
.
+If the __--verbose__ option is given, the message __Hmm...__ indicates that there is unprocessed text in the patch file and that __patch__ is attempting to intuit whether there is a patch in that text and, if so, what kind of patch it is.
-Conversely, in POSIX
__patch__, backups
-never made
, even when
there is a mismatch. In
-GNU __
patch__, this behavior is enabled
-with the __--no-backup-if-mismatch__ option, or by
-conforming
to POSIX with the __--posix__
-option or by setting the __POSIXLY_CORRECT__ environment
-variable
.
+__patch__'s exit status is 0 if all hunks
are applied successfully
, 1 if some hunks cannot be applied, and 2 if
there is more serious trouble. When applying
a set of patches in a loop it behooves you to check this exit status so you don't apply a later
patch to a partially patched file
. !!CAVEATS
+Context diffs cannot reliably represent the creation or deletion of empty files, empty directories, or special files such as symbolic links. Nor can they represent changes to file metadata like ownership, permissions, or whether one file is a hard link to another. If changes like these are also required, separate instructions (e.g. a shell script) to accomplish them should accompany the patch.
-The
__-b
__ ''suffix'' option of traditional
-patch
__ is equivalent
to the __-b -z__ ''suffix''
-options of GNU __
patch__
.
+__patch
__ cannot tell if the line numbers are off in an
__ed
__ script, and can detect bad line numbers in a normal diff only when it finds a change or deletion. A context diff using fuzz factor 3 may have the same problem. Until a suitable interactive interface
is added, you should probably do a context diff in these cases
to see if the changes made sense. Of course, compiling without errors is a pretty good indication that
the patch worked, but not always
.
+__patch__ usually produces the correct results, even when it has to do a lot of guessing. However, the results are guaranteed to be correct only when the patch is applied to exactly the same version of the file that the patch was generated from.
-Traditional __patch__ used a complicated (and
-incompletely documented) method to intuit the name of the
-file to be patched from the patch header. This method did
-not conform to POSIX , and had a few gotchas.
-Now __patch__ uses a different, equally complicated (but
-better documented) method that is optionally
-POSIX -conforming; we hope it has fewer
-gotchas. The two methods are compatible if the file names in
-the context diff header and the __Index:__ line are all
-identical after prefix-stripping. Your patch is normally
-compatible if each header's file names all contain the same
-number of slashes.
+!!Compatibility Issues
+The POSIX standard specifies behavior that differs from __patch__'s traditional behavior. You should be aware of these differences if you must interoperate with __patch__ versions 2.1 and earlier, which do not conform to POSIX .
-When
traditional __patch__ asked the user a question
, it
-sent
the question to standard error and looked for an answer
-from the first file in the following list that
was a
-terminal: standard error, standard output
, __/dev/tty
__,
-standard input. Now
__patch
__ sends questions
to
-standard output and gets answers from
__/dev/tty
__.
-Defaults for some answers have been changed so that
-patch
__ never goes into an infinite loop when using
-default answers
.
+In
traditional __patch__, the __-p__ option's operand
was optional
, and a bare
__-p
__ was equivalent to __-p0.__ The __-p__ option now requires an operand
, and __-p
__ is now equivalent
to __-p0
__. For maximum compatibility, use options like
__-p0__ and __-p1
__.
+Also, traditional __patch__ simply counted slashes when stripping path prefixes; __patch__ now counts pathname components. That is, a sequence of one or more adjacent slashes now counts as a single slash. For maximum portability, avoid sending patches containing __//__ in file names.
-Traditional
__patch__ exited
with a status value that
-counted
the number of bad hunks,
or with status 1 if there
-was real trouble. Now
__patch
__ exits with status 1 if
-some hunks failed, or with 2 if there was real
-trouble
.
+In traditional
__patch__, backups were enabled by default. This behavior is now enabled
with the __-b__
or __--backup
__ option
.
+Conversely, in POSIX __patch__, backups are never made, even when there is a mismatch. In GNU __patch__, this behavior is enabled with the __--no-backup-if-mismatch__ option, or by conforming to POSIX with the __--posix__ option or by setting the __POSIXLY_CORRECT__ environment variable.
-Limit yourself to the following options when sending
-instructions meant to be executed by anyone running
-GNU
__patch
__,
traditional __patch__,
-or a
__patch__ that conforms to POSIX .
-Spaces are significant in the following list, and operands
-are required
.
+The
__-b
__ ''suffix'' option of
traditional __patch__ is equivalent to the __-b -z__ ''suffix'' options of GNU
__patch__.
+Traditional __patch__ used a complicated (and incompletely documented) method to intuit the name of the file to be patched from the patch header. This method did not conform to POSIX , and had a few gotchas. Now __patch__ uses a different, equally complicated (but better documented) method that is optionally POSIX -conforming; we hope it has fewer gotchas. The two methods are compatible if the file names in the context diff header and the __Index:__ line are all identical after prefix-stripping. Your patch is normally compatible if each header's file names all contain the same number of slashes.
-__ -c
--d
__ ''dir
-''
__ -D
__ ''define
-''
__ -e
--l
--n
--N
--o
__ ''outfile
-''
__ -p
__''num
-''
__ -R
--r
__ ''rejectfile
-''
-!!BUGS
+When traditional
__patch
__ asked the user a question, it sent the question to standard error and looked for an answer from the first file in the following list that was a terminal: standard error, standard output,
__/dev/tty
__, and standard input. Now
__patch
__ sends questions to standard output and gets answers from
__/dev/tty
__. Defaults for some answers have been changed so that
__patch
__ never goes into an infinite loop when using default answers.
-Please report bugs via email to
-
+Traditional
__patch
__ exited with a status value that counted the number of bad hunks, or with status 1 if there was real trouble. Now __patch__ exits with status 1 if some hunks failed, or with 2 if there was real trouble
.
-__patch__ could be smarter about partial matches
,
-excessively deviant offsets and swapped code
, but
that would
-take an extra pass
.
+Limit yourself to the following options when sending instructions meant to be executed by anyone running GNU
__patch__, traditional __patch__
, or a __patch__
that conforms to POSIX . Spaces are significant in the following list, and operands are required
.
+* -c
+* -d dir
+* -D define
+* -e
+* -l
+* -n
+* -N
+* -o outfile
+* -pnum
+* -R
+* -r rejectfile
-If code has been duplicated (for instance with __#ifdef
-OLDCODE__ ... __#else ... #endif__), __patch__ is
-incapable of patching both versions, and, if it works at
-all, will likely patch the wrong one, and tell you that it
-succeeded to boot.
+!!Bugs
+Please report bugs via email to <bug-gnu-utils@gnu.org>.
-If you apply a patch you've already applied,
__patch__
-thinks it is a reversed patch
, and offers to un-apply the
-patch. This could be construed as a feature
.
-!!COPYING
+__patch__ could be smarter about partial matches
, excessively deviant offsets
and swapped code, but that would take an extra pass
.
+If code has been duplicated (for instance with __#ifdef OLDCODE__ ... __#else ... #endif__), __patch__ is incapable of patching both versions, and, if it works at all, will likely patch the wrong one, and tell you that it succeeded to boot.
-Copyright 1984
, 1985
, 1986, 1988 Larry Wall
.
-Copyright 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
-1997, 1998 Free Software Foundation, Inc
.
+If you apply a patch you've already applied
, __patch__ thinks it is a reversed patch
, and offers to un-apply the patch
. This could be construed as a feature
.
+!!Copying
-Permission is granted to make and distribute verbatim copies
-of this manual provided the copyright notice and this
-permission notice are preserved on all copies
.
+Copyright 1984, 1985, 1986, 1988 Larry Wall. Copyright 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998 Free Software Foundation, Inc
.
+Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies.
-Permission is granted to copy and distribute modified
-
-
-
-
+Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
+Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the copyright holders instead of in the original English.
-Permission is granted to copy and distribute translations of
-this manual into another language, under the above
-conditions for modified versions, except that this
-permission notice may be included in translations approved
-by the copyright holders instead of in the original
-English.
-AUTHORS
+!!Authors
+Larry Wall wrote the original version of __patch__. Paul Eggert removed __patch__'s arbitrary limits; added support for binary files, setting file times, and deleting files; and made it conform better to POSIX . Other contributors include Wayne Davison, who added unidiff support, and David !MacKenzie, who added configuration and backup support.
-Larry Wall wrote the original version of __patch__. Paul
-Eggert removed __patch__'s arbitrary limits; added
-support for binary files, setting file times, and deleting
-files; and made it conform better to POSIX .
-Other contributors include Wayne Davison, who added unidiff
-support, and David !MacKenzie, who added configuration and
-backup support.
----
+!! WLUG Notes
+See also the PatchNotes page.
