I find an ability to handle several .cvsrc files to be very valuable. If a proper .cvsrc is published with a build, it becomes possible to define default branches for each release. If CVSRC_PATH=/etc:~:$BUILD, then /etc/.cvsrc is sourced first to get installation wide defaults, then ~/.cvsrc, then $BUILD/.cvsrc. Eugene. : From: Gerhard Sittig [mailto:[EMAIL PROTECTED]] : Sent: Saturday, February 24, 2001 11:56 PM : : [ reformatted for readability ] : : On Sat, Feb 24, 2001 at 14:21 -0800, Rob Helmer wrote: : > : > On Sat, Feb 24, 2001 at 08:42:24AM -0500, Derek R. Price wrote: : > > : > > No, but you could link each user's ~/.cvsrc to some shared : > > cvsrc, I suppose. They couldn't make their own : > > customizations then, though. : > : > Ah, well. Might as well have .cvsrc copied into the home : > directory at the time the account is created, containing my : > defaults; that way users can modify them. : : And yet I feel having both ~/.cvsrc as well as /etc/cvsrc to be : of value. Has somebody already done this? Should I dig into : src/cvsrc.c a little deeper and contribute what I can come up : with? _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
