From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Storm-Olsen Subject: Re: [GIT-P4] usage under Windows Date: Wed, 27 Feb 2008 23:32:12 +0100 Message-ID: <47C5E4EC.1060003@trolltech.com> References: <96c268400802212244g7fd2de2bj6c1b7022885c8e89@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig37E8E8DF82B5BA009E226D39" Cc: git@vger.kernel.org To: Maxim Gordienko X-From: git-owner@vger.kernel.org Wed Feb 27 23:33:16 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1JUUph-0004Es-Vf for gcvg-git-2@gmane.org; Wed, 27 Feb 2008 23:33:02 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752628AbYB0WcZ (ORCPT ); Wed, 27 Feb 2008 17:32:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755530AbYB0WcZ (ORCPT ); Wed, 27 Feb 2008 17:32:25 -0500 Received: from hoat.troll.no ([62.70.27.150]:32835 "EHLO hoat.troll.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752092AbYB0WcY (ORCPT ); Wed, 27 Feb 2008 17:32:24 -0500 Received: from localhost (localhost [127.0.0.1]) by hoat.troll.no (Postfix) with ESMTP id 59E27581AA; Wed, 27 Feb 2008 23:31:40 +0100 (CET) Received: from hoat.troll.no ([127.0.0.1]) by localhost (hoat.troll.no [127.0.0.1]) (amavisd-maia, port 10024) with LMTP id 00761-10; Wed, 27 Feb 2008 23:31:40 +0100 (CET) Received: from [172.20.1.78] (unknown [172.20.1.78]) by hoat.troll.no (Postfix) with ESMTP id D21FE5819E; Wed, 27 Feb 2008 23:31:39 +0100 (CET) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: <96c268400802212244g7fd2de2bj6c1b7022885c8e89@mail.gmail.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=34EB4437 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEXU1NTAwMABAQGsrKyE hIQwMDAEBAS8hGUfAAACQUlEQVQ4jV2TS47cMAxEKSDZW1CfwMB4PYLkrKchsveJRR2gEen+R0hR 9vziBmahhyqSRQ4NfF1FmIv3dH4usNAGoFprBVguQJmZ1nX0XiHgEukTCK3TairiZeXcVGzmZIoU 3738pehdVbiU9KFgMQWeZ1fpHZDfRS4rPb3eQVaZChGx4ikt5GDkAZQ2KKohzjklno4+iJpVhxka ZjSpasJ4gdGaEQMWTMjRa5uTqza0XDJjzhIdzGTMrqoopimoIPCKZtVOq265MAXpMLXycmVl2Y8C oE1FkT/faKauOjYoHJyOxHfvixjowvI0xZJsKykubgLYzuJMdBO+L86TjxfQ9hz9jpSudbnXXzRm tor5i3MUONpOfARAhlWbzWF7OhP2eSeEW9HUBNiHOxUM8HLWHhUAj3NZNsdqRZpNA+DJ+XlX+Qc9 Z4ZjHX8LRUzgTBBef84NQoCMOcS0+BMsj3klbTzRri03ugXr9em1GfgzDAyEn4J3fvFI5YwdTrYu 1ntAY1h5ysM2OMGm+cBOocCXHisAHu2PagnLghoG2krz8bzsA4fj7KxCGk+63jt+DDCtYjbFNkHD nRwpRqsQYx5WYzsbm/eBfn0I4TbOGvMWqhQAiEDzNs4apumCI0x2OyHtY7uAlZff/sanbH9+AGT1 KOEmUlJISdYPgEgehw+cTZEf6xeFyoEjCPgv+A62KhW3EOy9PL7WmCBMRWmfYN0OqW9krzl/Ay91 75HMqfDtP8UFckFUX2rwrm/kTVB2gH+hdu4avZVCuAAAAABJRU5ErkJggg== X-Virus-Scanned: Maia Mailguard 1.0.2a Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig37E8E8DF82B5BA009E226D39 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Maxim Gordienko wrote: > What are best practices to use git-p4 under windows? > What p4 client should i use, native or cygwin one? Is any special > perforce client configuration required? > What python distribution is preferred, included in cygwin or active=20 python? Depends on what your system is. Are you using Git under Cygwin or MSys?=20 If you're using Cygwin normally, it's probably wise to use the cygwin=20 version of perforce too. Here's what I do: 1) Use MSys Git. It's faster. (http://code.google.com/p/msysgit/) 2) Use native Perforce. It's faster. 3) Get Python from python.org. There's a binary installer. > Where i need to put imported directory under perforce client' root or > in any other place? In perforce create your client spec somewhere where you don't see it.=20 You never need to touch these files, but they are needed to be able to=20 submit back to the perforce depot, if you need that. For cloning a=20 perforce depot, you don't need a checkout (git-p4 used 'p4 print' to get = the files directly) Keep in mind to always rebase your patches before submitting back to a=20 Perforce depot, since merges can be represented properly. So, a good=20 work practice is to 1) Clone perforce branch 2) work, work, commit, work, commit... 3) git p4 rebase 4) git p4 submit Good luck! -- =2Emarius --------------enig37E8E8DF82B5BA009E226D39 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) iD8DBQFHxeTwKzzXl/njVP8RAl1fAJ0ad7qGybuqXks1ztS46v8gfufIsACdGOgO buq1S6M7w2W1DWdWn/yP7Rk= =0QUN -----END PGP SIGNATURE----- --------------enig37E8E8DF82B5BA009E226D39--