Date: Sat, 24 Jun 2006 00:56:34 +0200 From: Erwin Lansing <erwin@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: RT 3.6.0 port Message-ID: <20060623225634.GW98272@droso.net> In-Reply-To: <61884E0C-D13C-42D4-84F9-1C41CCA5EE30@khera.org> References: <61884E0C-D13C-42D4-84F9-1C41CCA5EE30@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--mT/EkForZZEIFsY4 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 23, 2006 at 05:04:36PM -0400, Vivek Khera wrote: >=20 > Also, I've requested a repo copy of rt34 into rt36 for historical =20 > purposes, but I'm not sure that's really necessary. It seems to me =20 > we could just make a new port from scratch. Any opinions on that? >=20 If a new port shared the history of an existing port, usually by being a newer or development version of a stable port, we do a repocopy for starting the new port to preserve that history. Without looking at the patch, I'd say that this rule goes for the rt34 to rt36 move as well. Unless the new source is completely unrelated to the old one, a repocopy is the way to go. Cheers, -erwin --=20 Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_/// erwin@FreeBSD.org And it makes you cry. <____) (____> erwin@aauug.dk --mT/EkForZZEIFsY4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEnHGiqy9aWxUlaZARAqQaAJ9sa5sL9oXfrslL/oS+GOfIRwd8pQCgki06 y9Uif0qFrZZODskeXAFZW1E= =XyjL -----END PGP SIGNATURE----- --mT/EkForZZEIFsY4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060623225634.GW98272>