From owner-cvs-src@FreeBSD.ORG Fri Feb 20 13:55:25 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F88C16A4CE; Fri, 20 Feb 2004 13:55:25 -0800 (PST) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F07C243D2F; Fri, 20 Feb 2004 13:55:24 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i1KLtMnI000896; Fri, 20 Feb 2004 16:55:22 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040220.143945.93360906.imp@bsdimp.com> References: <200402201525.i1KFPuot051623@repoman.freebsd.org> <20040220.143945.93360906.imp@bsdimp.com> Date: Fri, 20 Feb 2004 16:55:21 -0500 To: "M. Warner Losh" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src UPDATING X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2004 21:55:25 -0000 At 2:39 PM -0700 2/20/04, M. Warner Losh wrote: >In message: > Garance A Drosihn writes: >: >: Did you get my email pointing out that the UPDATING entry for >: 20030714 should be updated? The problem that describes was >: solved a short time later. I have friends who read that entry, >: and think that they have to avoid -j on buildworlds... > >Yes. I've not had the chance to know when the date of safety >is, so haven't added one. This problem was addressed in revision 1.15 of http://www.freebsd.org/cgi/cvsweb.cgi/src/rescue/rescue/Makefile (On Aug 1 2003) People may still have problems with -j after that date, due to other new and exciting reasons. But if they do, then adding NO_RESCUE to their makefile will not change whatever problem they are seeing. I can say that I have been using -j since that date, with rescue always being built, and have not seen any problems. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu