Date: Sun, 25 Jan 2004 20:47:00 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Wes Peters <wes@softweyr.com> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/fetch fetch.1 Message-ID: <20040126044700.GA11530@dragon.nuxi.com> In-Reply-To: <200401251909.45346.wes@softweyr.com> References: <200401230450.i0N4omSZ049990@repoman.freebsd.org> <40123A86.3040102@aueb.gr> <xzp1xppt08v.fsf@dwp.des.no> <200401251909.45346.wes@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040126044700.GA11530>