Just to clarify a NetBSD 4.0 vs netbsd-4 issue for the
 	record - I think everyone involved in the conversation
 	already knows this, but for anyone else reading:

 	NetBSD 4.0, 4.1 and other NetBSD-4.* releases are (or will
 	be) fixed tags on the netbsd-4 release branch. A release
 	branch is created from -current at an appropriate point.

 	If a pullup/change is submitted too close to a given tag
 	then it will be held until after that tag has been applied
 	and which point it could be applied to the branch, and
 	obviously be picked up by the next tag.

 	I believe this is why Bucky is concerned about getting his
 	OMAP changes into netbsd-4 'for 4.0', so he can get a
 	workable NetBSD tree to base from now, rather than some
 	indeterminate point in the future after NetBSD 4.0 has been
 	released.

 	On that note - a NetBSD release-* branch is expected to be
 	an ideal point for an external party to base their use of
 	a NetBSD tree - it should _always_ be compilable and stable,
 	and any exception to this is resolved as quickly as possible.

 	The NetBSD -current tree is more often than not stable
 	enough to run on production servers, but there is no such
 	guarantee of this, and it can occcasionally be quite unstable
 	as a large change is merged and settled.

 	Of course, having a large set of submitted changes sit in
 	limbo seemingly indefinitely (as Bucky had) is hardly an
 	ideal introduction to the NetBSD branching and release
 	procedure. Apologies again for that.

-- 
 		David/absolute       -- www.NetBSD.org: No hype required --