On Tue, Jan 10, 2012 at 01:41:10PM +0700, Robert Elz wrote:
> __NetBSD_Version__ - I assume it is (attempting to be) maintained as
> a single source shared between NetBSD & other *BSD's (and more?) and
> so is almost better treated as if it were as below. (If that's no longer
> true I'd submit th
Date:Tue, 10 Jan 2012 03:48:31 + (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
Quoting Soren Jacobsen |>
| >My thinking was that we didn't care much if the version number got
| >bumped unless there was an API/ABI change.
It wasn't just when i
In article <20120110014214.ga14...@blef.org>,
Soren Jacobsen wrote:
>On 01/09 19:08, Robert Elz wrote:
>> Could someone who knows please explain the rules for the construction
>> of __NetBSD_Version__ for releases, what the sub-fields are, and how
>> they're actually used - and then perhaps actua
On 01/09 19:08, Robert Elz wrote:
> Could someone who knows please explain the rules for the construction
> of __NetBSD_Version__ for releases, what the sub-fields are, and how
> they're actually used - and then perhaps actually put that information
> into param.h ?
Well, I've made all of the 5.x
On Mon, Jan 09, 2012 at 07:08:44PM +0700, Robert Elz wrote:
> ps: I'd still like to see __NetBSD_Prereq__() macro destroyed.
so would I.
--
David A. Holland
dholl...@netbsd.org
I don't understand how __NetBSD_Version__ is supposed to operate
(other than the way it is used in -current - that part is no
mystery) - that is, how it is used in NetBSD releases.
The documentation (which as far as I can ascertain is just what
is in src/sys/sys/param.h) no longer seems to match c
