Date: Tue, 13 Jan 2004 19:37:32 +0100 From: Erwin Lansing <erwin@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Status reports - why not regularly? Message-ID: <20040113183732.GB69937@droso.net> In-Reply-To: <20040113183250.GB48706@voodoo.oberon.net> References: <20040113093903.GA84055@mimoza.pantel.net> <400409F4.3090205@freebsd.org> <400428DC.2060108@theatre.msu.edu> <20040113181911.GB432@jenny.daemon.li> <20040113182201.GA48706@voodoo.oberon.net> <400438CB.8030702@theatre.msu.edu> <20040113183250.GB48706@voodoo.oberon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jan 13, 2004 at 07:32:50PM +0100, Kirill Ponomarew wrote:
> Hi,
>=20
> On Tue, Jan 13, 2004 at 01:28:27PM -0500, Jonathan T. Sage wrote:
> > Exactally, and as Mark pointed out, I think that keeping in changes to=
=20
> > the ports infrastructure (bsd.ports.mk) would be an excellent idea.
>=20
> Yes, I think portmgr@ should mail to ports@ and explain the
> most important updates to bsd.*.mk
>=20
I am working on a plan to document major changes in about the same style
as for src. That is, a file /usr/src/CHANGES with important information
to developers (bsd.*.mk and port changes that affect a lot of other
porss) and adding a section to Release Notes on the web site with
information to ports users.
--=20
_._ _,-'""`-._
Erwin Lansing (,-.`._,'( |\`-/| erwin@lansing.dk
http://droso.org `-.-' \ )-`( , o o) erwin@FreeBSD.org
-bf- `- \`_`"'-
--k1lZvvs/B4yU6o8G
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFABDrrqy9aWxUlaZARArI4AKCT+7ip0CkqLgRVOt6XY3XphjyHKACggHbb
/342/gCRzmzN5n+I6ujSOdU=
=5Q5o
-----END PGP SIGNATURE-----
--k1lZvvs/B4yU6o8G--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040113183732.GB69937>