From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 10:32:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E47C316A4CE for ; Tue, 13 Jan 2004 10:32:52 -0800 (PST) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id B071543D4C for ; Tue, 13 Jan 2004 10:32:51 -0800 (PST) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.30) id 1AgTLO-000Cqt-Lv; Tue, 13 Jan 2004 19:32:50 +0100 Date: Tue, 13 Jan 2004 19:32:50 +0100 From: Kirill Ponomarew To: "Jonathan T. Sage" Message-ID: <20040113183250.GB48706@voodoo.oberon.net> Mail-Followup-To: Kirill Ponomarew , "Jonathan T. Sage" , Josef El-Rayes , freebsd-current@freebsd.org 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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE" Content-Disposition: inline In-Reply-To: <400438CB.8030702@theatre.msu.edu> X-NCC-Regid: de.oberon Sender: Kirill Ponomarew cc: freebsd-current@freebsd.org cc: Josef El-Rayes Subject: Re: Status reports - why not regularly? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 18:32:53 -0000 --xXmbgvnjoT4axfJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, 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. Yes, I think portmgr@ should mail to ports@ and explain the most important updates to bsd.*.mk -Kirill --xXmbgvnjoT4axfJE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFABDnSQC1G6a60JuURAvYdAJ9PR5e2p7wJupOtjSW1aK2KiqBdYgCeNnr8 s1PtCtLIJtogTjqp6fbE8a8= =3ykf -----END PGP SIGNATURE----- --xXmbgvnjoT4axfJE--