[BACK]Return to patch.1 CVS log [TXT][DIR] Up to [local] / src / usr.bin / patch

Diff for /src/usr.bin/patch/patch.1 between version 1.25 and 1.26

version 1.25, 2009/02/08 17:33:01 version 1.26, 2010/09/03 11:09:29
Line 603 
Line 603 
 .Nm  .Nm
 prompts the user  prompts the user
 .El  .El
 .Sh DIAGNOSTICS  .Sh EXIT STATUS
 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  
 The  The
 .Nm  .Nm
 utility exits with one of the following values:  utility exits with one of the following values:
 .Pp  .Pp
 .Bl -tag -width Ds -compact -offset indent  .Bl -tag -width Ds -offset indent -compact
 .It \&0  .It 0
 Successful completion.  Successful completion.
 .It \&1  .It 1
 One or more lines were written to a reject file.  One or more lines were written to a reject file.
 .It \*[Gt]\&1  .It \*(Gt1
 An error occurred.  An error occurred.
 .El  .El
 .Pp  .Pp
 When applying a set of patches in a loop it behooves you to check this  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.  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  .Sh SEE ALSO
 .Xr diff 1  .Xr diff 1
 .Sh STANDARDS  .Sh STANDARDS

Legend:
Removed from v.1.25  
changed lines
  Added in v.1.26