Received: by taz.hyperreal.com (8.6.12/8.6.5) id JAA11862; Thu, 2 May 1996 09:52:29 -0700 Received: from madhaus.utcs.utoronto.ca by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id JAA11853; Thu, 2 May 1996 09:52:26 -0700 From: rasmus@madhaus.utcs.utoronto.ca Received: from rathaus (rathaus [128.100.102.12]) by madhaus.utcs.utoronto.ca (8.7.4/8.7.1) with SMTP id MAA27578 for ; Thu, 2 May 1996 12:51:58 -0400 (EDT) Date: Thu, 2 May 1996 12:51:58 -0400 (EDT) Subject: Re: background CGI bug To: new-httpd@hyperreal.com In-Reply-To: <199605021613.AA178713623@ooo.lanl.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > This highlights a problem with the CVS way of doing things. > During periods of rapid change, we need to encourage everyone to > download snaphots on a regular basis. Which would be a heck of a lot easier if there was read-only CVS access. I saw the changes and ftp'ed the entire from-cvs beast once a day. Would have been much simpler to get the patches directly with a "cvs update". And it is much simpler to investigate individual patches. I know it can still be done by looking at each patch coming from the notification mailing list and applying them manually, but that requires a lot of effort and brain cycles. And once applied, it isn't extremely easy to revert back to older copies of the tree without CVS. I agree that CVS is not a good general-purpose distribution method, but for heavy testing/debugging purposes it is great. I know I would help out in finding this CGI bug if I had a bit better access to the sources and the individual changes. -Rasmus