From owner-p4-releng Fri Oct 18 13:37:18 2002 Delivered-To: p4-releng@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 4EFBF37B404; Fri, 18 Oct 2002 13:37:16 -0700 (PDT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDD1F37B401; Fri, 18 Oct 2002 13:37:15 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C366C43E9E; Fri, 18 Oct 2002 13:37:14 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g9IKahOo054269; Fri, 18 Oct 2002 16:36:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 18 Oct 2002 16:36:43 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Bruce A. Mah" Cc: Perforce Change Reviews Subject: Re: PERFORCE change 19567 for review In-Reply-To: <200210181843.g9IIh6e1070259@repoman.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-p4-releng@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just FYI, since it wasn't necessary, you can do your own repo copy using: p4 integ [oldfile] [newfile] Optionally, you can specify versions, etc. "p4 help integ" for more information. One of the big advantages to Perforce over CVS is that the notion of a repo copy is not only exported to users as a feature, but you can pull over new changes in the original file using further integs and it will help you merge. It's not quite the same as a real "rename" function, but it's still useful. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories On Fri, 18 Oct 2002, Bruce A. Mah wrote: > http://perforce.freebsd.org/chv.cgi?CH=19567 > > Change 19567 by bmah@bmah_tomcat on 2002/10/18 11:42:41 > > Add a paragraph about scrubbing /usr/include. > > Try to use P4 RCS tag, rather than FreeBSD. > > Affected files ... > > .. //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#2 edit > > Differences ... > > ==== //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#2 (text+ko) ==== > > @@ -23,7 +23,7 @@ > The FreeBSD Release Engineering Team > > > - $FreeBSD$ > + $P4: //depot/releng/doc/en_US.ISO8859-1/early-adopter-50/article.sgml#2 $ > > > 2002 > @@ -333,6 +333,16 @@ > Thus, using old ports may be > possible. > > + When installing or upgrading over the top of an existing > + 4-STABLE-based system, it is extremely important to clear out > + old header files in /usr/include. > + Renaming or moving this directory before a binary installation > + or an installworld is generally > + sufficient. If this step is not taken, confusion may result > + (especially with C++ programs) as the compiler may wind up > + using obsolete header files mixed in with the (intended) > + up-to-date ones. > + > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-releng" in the body of the message