6205 onbld manuals should be declared as 1onbld
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>

          --- old/usr/src/tools/scripts/bringovercheck.1.man.txt
          +++ new/usr/src/tools/scripts/bringovercheck.1onbld.man.txt
   1      -bringovercheck(1)                User Commands               bringovercheck(1)
        1 +bringovercheck(1ONBLD)        illumos Build Tools       bringovercheck(1ONBLD)
   2    2  
   3    3  
   4    4  
   5    5  NAME
   6    6         bringovercheck - Repair misordered workspace timestamps
   7    7  
   8    8  SYNOPSIS
   9    9         bringovercheck workspace
  10   10  
  11   11  DESCRIPTION
  12      -       Some versions of bringover(1) fail to msync(2) writeable mappings; this
  13      -       results in indeterminate modification times when the workspace exists
  14      -       on certain filesystems.  When this results in SCCS s. files being newer
  15      -       than their respective checked-out source files, build carnage may
  16      -       result (see sccscheck(1) for one mitigating step being taken).
       12 +       Some versions of bringover(1ONBLD) fail to msync(2) writeable mappings;
       13 +       this results in indeterminate modification times when the workspace
       14 +       exists on certain filesystems.  When this results in SCCS s. files
       15 +       being newer than their respective checked-out source files, build
       16 +       carnage may result (see sccscheck(1ONBLD) for one mitigating step being
       17 +       taken).
  17   18  
  18   19         If a workspace has been damaged by this bug, you can run bringovercheck
  19   20         to detect and correct cases where a source file is older than its
  20   21         corresponding SCCS s. file.
  21   22  
  22   23         If no out-of-date files are found, bringovercheck will produce no
  23   24         output; otherwise, it will produce a human-readable transcript which
  24   25         includes filenames, last modification dates, and the output of the sccs
  25   26         commands it uses to attempt to fix the problem.
  26   27  
  27   28         Note that because the problem may involve deferred filesystem writes,
  28   29         this script may not be fully effective if run immediately after a
  29   30         bringover.
  30   31  
  31   32  
  32   33  
  33   34  
  34   35  
  35      -                                 7 April 2006                bringovercheck(1)
       36 +                                 7 April 2006           bringovercheck(1ONBLD)
    

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX