From owner-freebsd-current Mon Mar 6 1:19:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 363EB37BCCE; Mon, 6 Mar 2000 01:19:50 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA53194; Mon, 6 Mar 2000 02:19:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA57690; Mon, 6 Mar 2000 02:19:40 -0700 (MST) Message-Id: <200003060919.CAA57690@harmony.village.org> To: Garance A Drosihn Subject: Re: ssh strangeness in -current... Cc: John Baldwin , Kris Kennaway , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 03:17:51 EST." References: <200003060423.XAA01323@server.baldwin.cx> Date: Mon, 06 Mar 2000 02:19:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Garance A Drosihn writes: : My guess is that when he said "help someone to actually fix your problem", : his desire was to fix it so people would NOT have a problem updating. I've added a blurb to UPDATING. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message