===================================================================
RCS file: /cvsrepo/anoncvs/cvs/src/usr.bin/patch/patch.1,v
retrieving revision 1.28.2.1
retrieving revision 1.29
diff -u -r1.28.2.1 -r1.29
--- src/usr.bin/patch/patch.1	2015/07/27 16:10:54	1.28.2.1
+++ src/usr.bin/patch/patch.1	2015/03/13 19:58:41	1.29
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: patch.1,v 1.28.2.1 2015/07/27 16:10:54 krw Exp $
+.\"	$OpenBSD: patch.1,v 1.29 2015/03/13 19:58:41 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: July 27 2015 $
+.Dd $Mdocdate: March 13 2015 $
 .Dt PATCH 1
 .Os
 .Sh NAME
@@ -479,6 +479,15 @@
 file name, and choose the file name with the fewest path components,
 the shortest basename, and the shortest total file name length (in that order).
 .It
+If no file exists,
+.Nm
+checks for the existence of the files in an RCS directory
+(using the appropriate suffix) using the criteria specified
+above.
+If found,
+.Nm
+will attempt to get or check out the file.
+.It
 If no suitable file was found to patch, the patch file is a context or
 unified diff, and the old file was zero length, the new file name is
 created and used.
@@ -677,7 +686,7 @@
 If code has been duplicated (for instance with #ifdef OLDCODE ... #else ...
 #endif),
 .Nm
-is incapable of patching both versions, and, if it works at all, will likely
+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.
 .Pp
 If you apply a patch you've already applied,