Date: Sun, 16 Mar 2003 11:26:56 -0700 From: Nate Williams <nate@yogotech.com> To: Sergey Babkin <babkin@bellatlantic.net> Cc: hackers@FreeBSD.ORG Subject: Re: making CVS more convenient Message-ID: <15988.49648.483313.383942@emerger.yogotech.com> In-Reply-To: <3E73DCF7.80490FA6@bellatlantic.net> References: <3E73DCF7.80490FA6@bellatlantic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15988.49648.483313.383942>