--0OWHXb1mYLuhj1Ox
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 15, 2003 at 10:59:19AM +0200, Martin Weber wrote:
>=20
> Yes, but this way you could tag together the DATES of the releases.
> I.e.  when you have new stuff in 1.6.1B you can place a safe bet that
> this won't be in 1.6.1, while you have to look through the release
> announcement of 1.6.1 to see around which time of -current 1.6.1 was
> created and which of the features/bugs went into the release branch.

as i see it, it will only spread more confusion.  it looks like that
1.6.1A was created from 1.6.1 sources, which is not true.  1.6.1 is not
a "sync with -current", it's made from separate branch where only *some*
fixes from -current were pulled up.  you couldn't say from 1.6.1A which
features/bugs made it into netbsd-1-6 from -current either.


regards,

--=20
-- Lubomir Sedlacik <salo@Xtrmntr.org>                   --
--                  <salo@silcnet.org>                   --

--0OWHXb1mYLuhj1Ox
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE+m8vLiwjDDlS8cmMRAoi9AJ4nb6exAW+KOym6e0oO9cIkEt49iACeKTk+
8k1t0i7/o3hypBmFFCyncTc=
=JaWn
-----END PGP SIGNATURE-----

--0OWHXb1mYLuhj1Ox--