Date: Fri, 21 Feb 1997 08:28:32 -0800 From: John Polstra <jdp@polstra.com> To: asami@vader.cs.berkeley.edu (Satoshi Asami) Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-share@freefall.freebsd.org Subject: Re: cvs commit: src/share/doc/handbook cvsup.sgml Message-ID: <199702211628.IAA12790@austin.polstra.com> In-Reply-To: Your message of "Fri, 21 Feb 1997 00:18:08 PST." <199702210818.AAA02884@silvia.HIP.Berkeley.EDU> References: <199702210818.AAA02884@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
> * Add a section describing the available CVSup collections. I'm not > * wild about the way it looks, but at least the information is there. > > Don't we have an almost identical one in sup.sgml? Almost identical, but not identical. They're not tied together any more, like they used to be. I.e., supfilesrv (where it's still running at all) no longer uses the same config files as cvsupd. I don't really want them tied together. The CVSup mirrors are set up now so that if I add a new collection on freefall, it automagically propagates to all the mirrors -- the mirror maintainers don't have to do a thing. With sup, you get whatever a particular mirror maintainer happened to remember to add. > (Actually that one is more complete, as it contains comments on > what's what.) I can fix that. > I'm sure I'm going to forget adding a new ports collection if it's > duplicated in two places. Add it to cvsup.sgml first. :-) > (Actually, I won't cry my eyes out if sup.sgml just goes away...we > don't really support it anymore anyway.) I feel the same way about it. You're not going to see me investing much time keeping the sup stuff up to date, that's for sure. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702211628.IAA12790>