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

On Sun, Jun 18, 2006 at 11:02:19PM -0400, Brian A. Seklecki wrote:
> > they were sets from 3.0-RELEASE, the tags in the tree are for
> > 3.0-RELEASE, and running a plain `cvs update -Pd` just gets, well,
> > 3.0-RELEASE! So, in order to update the tree to 3.0.1, is it ok to
> > do a `cvs update -Pd -r netbsd-3-0`=20
>=20
> BTW, this will get you to the HEAD of the 3.x branch which is
> "3.0_STABLE".  Some CVS tags are "sticky" once set, so that may
> describe the behavior you're seeing.  Check /usr/src/CVS/Tag

not true.  it will get him "3.0.1" at the moment, "3.0.1_STABLE" later
(and "3.0.n[_STABLE]" in the future).

you are talking about netbsd-3 branch.

 http://netbsd.org/Releases/release-map.html


regards,

--=20
-- Lubomir Sedlacik <salo@{NetBSD,Xtrmntr,silcnet}.org>   --

--uh9ZiVrAOUUm9fzH
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFEllwYiwjDDlS8cmMRAi3kAJ44WvUQTHE89npE3T5GVW0mWr67mACcD5iL
+tP087LcIcUxh0L+gauAulQ=
=YNGp
-----END PGP SIGNATURE-----

--uh9ZiVrAOUUm9fzH--