Date: Mon, 01 Mar 2004 18:35:28 -0500 From: "Jonathan T. Sage" <sagejona@msu.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: questions@freebsd.org Subject: Re: HEADS UP: /usr/ports/UPDATING documents upgrade pitfalls Message-ID: <4043C8C0.3020104@msu.edu> In-Reply-To: <20040301223855.GA4591@xor.obsecurity.org> References: <20040301223855.GA4591@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig378C72BDD5D764B2DC537A0C Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Does this superseed /usr/ports/CHANGES? or co-exist? (just curious) ~j Kris Kennaway wrote: > FYI..everyone should get in the habit of checking this file for > changes after they update their ports tree. > > In particular, the inaugural entry addresses the problems many people > have experienced when trying to upgrade portupgrade. > > Kris *snip* -- Jonathan T. Sage Theatrical Lighting / Set Designer Professional Web Design [HTTP://www.JTSage.com] [sagejona@msu.edu] [See Headers for Contact Info] --------------enig378C72BDD5D764B2DC537A0C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAQ8jAoVmW2UUup/ERAkxRAJ4tGApgDI8c61GPRm/cpmFVBazALACfRc92 h0gEfGTve3jAI9F4W47oIQ0= =kWiH -----END PGP SIGNATURE----- --------------enig378C72BDD5D764B2DC537A0C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4043C8C0.3020104>