Re: kern/45935: Requested change to comments in sys/param.h

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR kern/45935; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/45935: Requested change to comments in sys/param.h
Date: Tue, 07 Feb 2012 01:31:42 +0700

     Date:        Mon,  6 Feb 2012 17:55:03 +0000 (UTC)
     From:        Alan Barrett <apb%cequrux.com@localhost>
     Message-ID:  <20120206175503.0B45963B86B%www.NetBSD.org@localhost>
 
   |  > Note: this patch also removes __NetBSD_Prereq__()
   |  I'd prefer to leave that for a separate change.
 
 I expected that...
 
   |  I like that, but will scripts that search for the comment be able to
   |  handle it?
 
 Not sure, nor am I sure what all the scripts are.   The one I use for
 kernel building which uses that value to construct the output directory
 name would not have a problem, it looks for the ' NetBSD ' in the comment
 and ignores everything before that.   But others, I'm not sure - and in
 any case, I think that should also be a separate change.
 
   |  Only two digits are reserved for "pp", so I think it should
   |  be restricted to [0..99].  Alternatively, remove "rr", and
   |  let "pppp" be 4 digits.
 
 It works either way, I just didn't want anyone to panic upon nearing
 5.99.99 and to be able to just continue on to 5.99.100 (and so on).
 It all works whether the 1 is considered as an unusual value in the r
 field or just a wider p field.   On the other hand, I can't even
 imagine the need for a 5.0.100 release (or even 5.0.10), so for everything
 other than current, 2 digits is really overkill already.
 
 But as I said, whatever works, just so there is some documented method
 that actually matches reality (which includes not always having 0's in the
 final 2 digit positions.)
 
 kre