From owner-freebsd-arch@FreeBSD.ORG Mon Aug 29 12:39:49 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5567B1065670 for ; Mon, 29 Aug 2011 12:39:49 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.paeps.cx (rincewind.paeps.cx [IPv6:2002:596a:f092::149]) by mx1.freebsd.org (Postfix) with ESMTP id 9A8478FC16 for ; Mon, 29 Aug 2011 12:39:48 +0000 (UTC) Received: from luggage.be.softathome.com (94-225-67-130.access.telenet.be [94.225.67.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: philip) by rincewind.paeps.cx (Postfix) with ESMTPSA id A4434D744E4; Mon, 29 Aug 2011 14:39:45 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Philip Paeps In-Reply-To: Date: Mon, 29 Aug 2011 14:39:46 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <3CE7269E-DDD8-4A28-9FCD-D8FEA3C89089@freebsd.org> References: <35765857-1314243257-cardhu_decombobulator_blackberry.rim.net-329610575-@b2.c15.bise7.blackberry> To: vadim_nuclight@mail.ru X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-arch@freebsd.org Subject: Re: Official git export X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 12:39:49 -0000 On 28 Aug 2011, at 23:18, Vadim Goncharov wrote: > On Fri, 26 Aug 2011 10:06:32 +0100 (BST); Robert Watson wrote about = 'Official git export (was: Re: FreeBSD problems and preliminary ways to = solve)': >> I have to admit I've always preferred Perforce to git, simply because = it=20 >> strikes me as a more structured approach, partial checkouts (but = especially=20 >> composition of different depot pieces in a single checkout to create = hybrid=20 >> trees), etc. But git is widely used, and quite effectively used, by = large=20 >> communities. We need to support those communities better. >=20 > I haven't worked with Perforce, do you mean I could checkout at once = several > directories e.g. sbin/ipfw and sys/netinet/ipfw in my working copy? If = so, > sounds good. Yes. Perforce is 'namespace-based'. You map parts of the repository = namespace into your client namespace and work from there. Branches are free for = most practical purposes and it's reasonably easy to merge between branches. The main downside of Perforce is that the server likes to track every = client's files and that things get very shaky when you try to interfere with that principle. One of my customers uses Perforce without tracking (or tries = to) and it goes horribly wrong in a number of ways (gigantic "p4 have" = databases, which don't reflect reality, accidental "p4 sync -k" locking up the = server for everyone for hours,...). > May be FreeBSD should really write it's own VCS, just as Git was > modelled after proprietary BitKeeper?.. I think git is a very reasonable system and it should be possible to map = the way we work with FreeBSD into git. As has been mentioned elsethread: = things would be a lot easier if we had "official git seeds" to pull from which would make it easy to collaborate and then push things up into SVN. = Also, a page of "rules for things not to do with git" would be helpful. It = would be a bad idea if committers using git pushed changes into Subversion which = made subversion impossible to use (or much harder to use than it currently = is). - Philip --=20 Philip Paeps Senior Reality Engineer Ministry of Information