Dave <[EMAIL PROTECTED]> writes: >We distribute our source to a remote location that does not have a network >connection to our main CVS repository host. We tar the CVS root on tape and >extract it on the remote host.
Strange. Does the remote site have to see the detailed revision history? If not, I would just use cvs export to send them tarballs of tagged releases. They can import the tarballs into their own independent CVS repository. They can send you patches when they make significant changes, and they can reimport and merge when you make significant changes. In other words, you pretend they are a privileged customer, they pretend you are a responsive vendor. >The problem is we need a way to capture the changes made during the >installation in our main CVS root. Your distribution method is unconventional, but they can still generate patches and send them to you. If you want tighter integration of the two sites, you're going to need some sort of network... -- Pierre Asselin Westminster, Colorado -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! -----== Over 80,000 Newsgroups - 16 Different Servers! =----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs