Maxim Gordienko wrote:
quoted text
> 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.

quoted text
> 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