summaryrefslogtreecommitdiffstats
path: root/usr.bin/patch/patch.1
diff options
context:
space:
mode:
authorjmc <jmc@openbsd.org>2010-09-03 11:09:28 +0000
committerjmc <jmc@openbsd.org>2010-09-03 11:09:28 +0000
commitf1c64ac4de90b4f8a835a7530957a2950b33193d (patch)
tree3c500e8cf145a59cdbfa1005c3487be92bac5773 /usr.bin/patch/patch.1
parentthib insists i take responsibility too (diff)
downloadwireguard-openbsd-f1c64ac4de90b4f8a835a7530957a2950b33193d.tar.xz
wireguard-openbsd-f1c64ac4de90b4f8a835a7530957a2950b33193d.zip
add an EXIT STATUS section for /usr/bin;
Diffstat (limited to 'usr.bin/patch/patch.1')
-rw-r--r--usr.bin/patch/patch.136
1 files changed, 18 insertions, 18 deletions
diff --git a/usr.bin/patch/patch.1 b/usr.bin/patch/patch.1
index 611d8981632..1861725775e 100644
--- a/usr.bin/patch/patch.1
+++ b/usr.bin/patch/patch.1
@@ -1,4 +1,4 @@
-.\" $OpenBSD: patch.1,v 1.25 2009/02/08 17:33:01 jmc Exp $
+.\" $OpenBSD: patch.1,v 1.26 2010/09/03 11:09:29 jmc Exp $
.\" Copyright 1986, Larry Wall
.\"
.\" Redistribution and use in source and binary forms, with or without
@@ -19,7 +19,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.Dd $Mdocdate: February 8 2009 $
+.Dd $Mdocdate: September 3 2010 $
.Dt PATCH 1
.Os
.Sh NAME
@@ -603,33 +603,33 @@ used to read input when
.Nm
prompts the user
.El
-.Sh DIAGNOSTICS
-Too many to list here, but generally indicative that
-.Nm
-couldn't parse your patch file.
-.Pp
-The message
-.Qq Hmm...
-indicates that there is unprocessed text in the patch file and that
-.Nm
-is attempting to intuit whether there is a patch in that text and, if so,
-what kind of patch it is.
-.Pp
+.Sh EXIT STATUS
The
.Nm
utility exits with one of the following values:
.Pp
-.Bl -tag -width Ds -compact -offset indent
-.It \&0
+.Bl -tag -width Ds -offset indent -compact
+.It 0
Successful completion.
-.It \&1
+.It 1
One or more lines were written to a reject file.
-.It \*[Gt]\&1
+.It \*(Gt1
An error occurred.
.El
.Pp
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.
+.Sh DIAGNOSTICS
+Too many to list here, but generally indicative that
+.Nm
+couldn't parse your patch file.
+.Pp
+The message
+.Qq Hmm...
+indicates that there is unprocessed text in the patch file and that
+.Nm
+is attempting to intuit whether there is a patch in that text and, if so,
+what kind of patch it is.
.Sh SEE ALSO
.Xr diff 1
.Sh STANDARDS