Date: Tue, 11 Sep 2001 14:50:55 -0500 From: Mike Meyer <mwm@mired.org> To: "Mark D. Anderson" <mda@discerning.com> Cc: <freebsd-hackers@freebsd.org> Subject: Re: local changes to CVS tree Message-ID: <15262.27423.830000.167832@guru.mired.org> In-Reply-To: <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke> References: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke> <01090920122401.00426@antiproton.ChrisBowman.com> <0d7201c13af1$dbcf74a0$6501a8c0@mdaxke>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark D. Anderson <mda@discerning.com> types: > as for the other areas you mention, perforce does not directly support repository-to-repository > replication, nor disconnected operations. > i do not know if perforce supports branching against a "remote depot"; i suspect something > like that would accomplish the same goal. > but maybe not. Perforce permits branching from a remote depot, but not to a remote depot - they are read-only. If the goal is to replicate the remote depot, this won't do it. If the goal is to keep local changes to remote depot, it works very well. It will require you to be online to do source udpates, though. While perforce doesn't let you work with it while disconnected, there is a simple procedure to integrate changes made locally while disconnected back to the depot. Personally, I'd love to have access to FreeBSD source via a perforce remote host. On the other hand, I'm biased. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. 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?15262.27423.830000.167832>