git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Marius Storm-Olsen <marius@trolltech.com>
To: Maxim Gordienko <mgordienko@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GIT-P4] usage under Windows
Date: Wed, 27 Feb 2008 23:32:12 +0100	[thread overview]
Message-ID: <47C5E4EC.1060003@trolltech.com> (raw)
In-Reply-To: <96c268400802212244g7fd2de2bj6c1b7022885c8e89@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

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 
python?

Depends on what your system is. Are you using Git under Cygwin or MSys? 
If you're using Cygwin normally, it's probably wise to use the cygwin 
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. 
You never need to touch these files, but they are needed to be able to 
submit back to the perforce depot, if you need that. For cloning a 
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 
Perforce depot, since merges can be represented properly. So, a good 
work practice is to
    1) Clone perforce branch
    2) work, work, commit, work, commit...
    3) git p4 rebase
    4) git p4 submit

Good luck!

--
.marius


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

  reply	other threads:[~2008-02-27 22:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  6:44 [GIT-P4] usage under Windows Maxim Gordienko
2008-02-27 22:32 ` Marius Storm-Olsen [this message]
2008-02-29 18:48   ` Maxim Gordienko
2008-02-29 21:54     ` Marius Storm-Olsen
2008-03-01  7:41       ` Maxim Gordienko
2008-03-01  9:50         ` Marius Storm-Olsen
2008-03-01 11:44     ` Tor Arvid Lund
2008-03-01 15:53       ` Marius Storm-Olsen
2008-03-03 19:24         ` Maxim Gordienko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47C5E4EC.1060003@trolltech.com \
    --to=marius@trolltech.com \
    --cc=git@vger.kernel.org \
    --cc=mgordienko@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).