From owner-cvs-all Tue Aug 31 14:33:37 1999 Delivered-To: cvs-all@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1936614E4A; Tue, 31 Aug 1999 14:33:30 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id OAA15340; Tue, 31 Aug 1999 14:33:29 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA03032; Tue, 31 Aug 1999 14:33:28 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 31 Aug 1999 14:33:28 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Doug Subject: Re: cvs commit: src/share/examples/cvsup cvs-supfile secure-cvs- Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Doug wrote: > On Tue, 31 Aug 1999, Chris Costello wrote: > >> Content-Description: Example of suggested cvsup file changes >> >> > --- stable-supfile.Dist Tue Aug 31 13:08:18 1999 >> > +++ stable-supfile Tue Aug 31 13:10:19 1999 >> > -*default delete use-rel-suffix >> > +*default delete use-rel-suffix umask=002 >> >> How about noting this in a comment instead of defaulting it? > > I'll leave that up to John, I have no pref either way. It's come > up on the list often enough that I thought it deserves some more attention > though. I think I prefer it uncommented, but on a line of its own so it's easier to comment out: *default delete use-rel-suffix *default umask=002 That would reduce the number of reports I get about zillions of SetAttr messages from people who run CVSup under varying umasks. The README file in the examples/cvsup directory should be updated to say that the supfiles work for versions 16.0 and later. Earlier versions didn't support the umask option. The comments you suggested for the crypto collections are a good idea too. My only suggestion there would be to change them a little bit so it's clear that, for example, Kerberos is in src-crypto *perhaps along with other stuff*. In other words, the src-crypto tree isn't defined by the fact that it contains Kerberos; it just so happens that Kerberos is the main thing in there currently. Likewise for DES and src-secure, though maybe Mark Murray should weigh in on exactly what does define that collection. There should be a similar comment for the new src-sys-crypto collection, such as "Export-restricted kernel code." I'm kind of backlogged at the moment, and now I have to start jury duty tomorrow (ick). If some other committer has time to make these changes, there certainly won't be any complaints from me. :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message