From owner-cvs-all@FreeBSD.ORG Sun Jan 25 20:47:15 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4351B16A4CE; Sun, 25 Jan 2004 20:47:15 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9012F43D2F; Sun, 25 Jan 2004 20:47:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0Q4l3A0026139; Sun, 25 Jan 2004 20:47:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0Q4l13J026138; Sun, 25 Jan 2004 20:47:01 -0800 (PST) (envelope-from obrien) Date: Sun, 25 Jan 2004 20:47:00 -0800 From: "David O'Brien" To: Wes Peters Message-ID: <20040126044700.GA11530@dragon.nuxi.com> References: <200401230450.i0N4omSZ049990@repoman.freebsd.org> <40123A86.3040102@aueb.gr> <200401251909.45346.wes@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401251909.45346.wes@softweyr.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Diomidis Spinellis cc: src-committers@FreeBSD.org cc: Ruslan Ermilov cc: Wes Peters cc: cvs-src@FreeBSD.org cc: Dag-Erling Sm?rgrav cc: Alfred Perlstein cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/fetch fetch.1 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 04:47:15 -0000 On Sun, Jan 25, 2004 at 07:09:45PM -0800, Wes Peters wrote: > > > While a user might find it helpful to read the environment variable > > > documentation in fetch(1), the correct thing to do in reference > > > material is to document the variables where they are implemented, > > > namely fetch(3), and provide a cross reference. > > > > Yes. I'd like to see Wes's commit backed out, please. > > Roger Wilco. Is it OK to make a stronger recommendation that the user > consult fetch(3) for some rather critical information about how fetch(1) > really works? That would be a good compromise. I've heard more than once one couldn't find the env vars to set for proxies, etc... in the fetch(1) manpage.