From owner-freebsd-hackers Sun Mar 16 10:27:13 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 849FB37B401 for ; Sun, 16 Mar 2003 10:27:12 -0800 (PST) Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37A1443FEC for ; Sun, 16 Mar 2003 10:26:59 -0800 (PST) (envelope-from nate@yogotech.com) Received: from emerger.yogotech.com (emerger.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA20452; Sun, 16 Mar 2003 11:26:57 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by emerger.yogotech.com (8.12.6/8.12.6) id h2GIQudA010109; Sun, 16 Mar 2003 11:26:56 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15988.49648.483313.383942@emerger.yogotech.com> Date: Sun, 16 Mar 2003 11:26:56 -0700 To: Sergey Babkin Cc: hackers@FreeBSD.ORG Subject: Re: making CVS more convenient In-Reply-To: <3E73DCF7.80490FA6@bellatlantic.net> References: <3E73DCF7.80490FA6@bellatlantic.net> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The idea is to support a "cache" repository (the one copied to a local > machine by CVSup or CTM) transparently. So that the reads from > directory will go from the local cache repository (and won't > overstrain the remote server, and will be fast too), while the commits > and other changes will go into the remote master repository. Good stuff. I wanted something like this *years* ago when we first started using CVS in FreeBSD. > The value specified in CVSROOTCACHE is the local path to the cache > repository. All the check-outs, updates, diffs etc. will be obtained > from there. All the check-ins, tagging etc. will go into the master > repository specified by CVSROOT. Naturally, to see these changes > in the cache repository, it needs to be updated by some outside > means such as CVSup or CTM. So, the cache doesn't automagically update itself when commits are done? This is less useful, since often-times after a commit has been done the user is still working in the same general area, so a 'cvs update' would now give the user older files since the read-only cache is not up-to-date, thus making it a requirement that everytime you make a commit, you also sychronize the cache. If this could be done automagically, it would make the cache more 'coherent' and things much more useful. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message