From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 14 03:56:17 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E901916A41A for ; Wed, 14 Nov 2007 03:56:17 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 8FC8F13C442 for ; Wed, 14 Nov 2007 03:56:17 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 17804 invoked by uid 1001); 14 Nov 2007 03:29:47 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Tue, 13 Nov 2007 22:29:46 -0500 Date: Tue, 13 Nov 2007 22:29:46 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20071113222946.58f314d4@bhuda.mired.org> In-Reply-To: <20071113194530.GA1281@kobe.laptop> References: <4733F1DA.60706@gmail.com> <1194616213.8643.24.camel@z60m.optimlabs.com> <1194619407.64797.64.camel@localhost> <1194621176.1219.3.camel@z60m.optimlabs.com> <4734B397.4010905@elischer.org> <20071113194530.GA1281@kobe.laptop> Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: keramida@freebsd.org Subject: Re: questions on development(7) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 03:56:18 -0000 On Tue, 13 Nov 2007 21:45:30 +0200 Giorgos Keramidas wrote: > > I wonder if ther is a way we could broadcast changes to the p4 'head' > > branch so that people could keep their own p4 servers up to date. > > Unfortunately, no. Perforce is not easy to 'mirror' around the world, > but it's ok. Actually, it is easy. Well, sort of, as whether or not what you're doing is a mirror depends on how you want to define 'mirror'. It looks and acts like a read-only local copy, but it isn't. Instead, your server fetches the bits it needs from the remote server on demand. > For a determined person, it should be fairly easy to set > up a local mirror of any part of the FreeBSD src tree, using one of > the distributed SCMs. They have *great* support for mirroring clones > of the original repository, and most of them have fairly good support > for incremental updates over the wire --- transferring the minimal > number of bits and bytes over a slow connection, they can keep an up to > date local clone of a remote tree. > > I don't know of anything which can do the same for Perforce depots; > which is unlucky, because it would help me *tremendously* in my every > day ${realjob} too. If anyone wants help with setting up Mercurial to > do something like this, however, I'm all for it and I will help in any > way I can. What you want to do is set up the master (where you are mirroring from) as a remote depot on your local server. You then treat the appropriate part of that as the "vendor branch". You treat it just like you'd treat a vendor branch most other SCMs - except you don't have to "import new vendor code". You need local changes? Create a local branch of the vendor branch, and work there. You need to merge vendor changes into your branch? You do it just like you would if it were in the local repository. You want to grovel through the change logs of the vendor branch? Those are there as well, just like they are in a distributed SCM. It isn't the same as having a local repository in a distributed SCM, so the advantages and disadvantages are different. Whether or not it'll do the job you want depends on the exact nature of the job. But I've been happy doing things this way. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. -- Mike Meyer http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.