===================================================================
RCS file: /cvsrepo/anoncvs/cvs/src/usr.bin/patch/patch.1,v
retrieving revision 1.3
retrieving revision 1.4
diff -c -r1.3 -r1.4
*** src/usr.bin/patch/patch.1	1998/11/25 00:30:25	1.3
--- src/usr.bin/patch/patch.1	1999/06/05 01:21:36	1.4
***************
*** 1,4 ****
! .\"	$OpenBSD: patch.1,v 1.3 1998/11/25 00:30:25 espie Exp $	-*- nroff -*-
  .rn '' }`
  .de Sh
  .br
--- 1,4 ----
! .\"	$OpenBSD: patch.1,v 1.4 1999/06/05 01:21:36 aaron Exp $	-*- nroff -*-
  .rn '' }`
  .de Sh
  .br
***************
*** 460,466 ****
  Second, make sure you've specified the filenames right, either in a
  context diff header, or with an Index: line.
  If you are patching something in a subdirectory, be sure to tell the patch
! user to specify a 
  .B \-p
  switch as needed.
  Third, you can create a file by sending out a diff that compares a
--- 460,466 ----
  Second, make sure you've specified the filenames right, either in a
  context diff header, or with an Index: line.
  If you are patching something in a subdirectory, be sure to tell the patch
! user to specify a
  .B \-p
  switch as needed.
  Third, you can create a file by sending out a diff that compares a
***************
*** 511,517 ****
  Check patch mode (
  .BR -C )
  will fail if you try to check several patches in succession that build on
! each other.  The whole code of 
  .I patch
  would have to be restructured to keep temporary files around so that it can
  handle this situation.
--- 511,517 ----
  Check patch mode (
  .BR -C )
  will fail if you try to check several patches in succession that build on
! each other.  The whole code of
  .I patch
  would have to be restructured to keep temporary files around so that it can
  handle this situation.