From owner-freebsd-current Fri Feb 25 2: 8:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 12F0737C1B4 for ; Fri, 25 Feb 2000 02:08:28 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA65259; Fri, 25 Feb 2000 02:08:18 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38B65491.5BB196CC@gorean.org> Date: Fri, 25 Feb 2000 02:08:17 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Munehiro Matsuda Cc: bloom@acm.org, freebsd-current@FreeBSD.ORG Subject: Re: mergemaster fail with crypto changes References: <20000225135218A.haro@tk.kubota.co.jp> <38B5FF33.DE8D6C6A@acm.org> <20000225153546A.haro@tk.kubota.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Munehiro Matsuda wrote: > > Well that does't seem to work for me. Becase mergemaster doesn't use > NOCRYPT stuff and /usr/src/crypto doesn't exist by default, if you > just cvsup (or use CTM for my case). > > I think checking for crypto is just simple. It probably will be, but we all need time to adjust to these massive changes. Please give me a little time to get my source tree, etc. up to date. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message