On 3 November 2011 01:43, Vitor Antunes <vitor.hda@xxxxxxxxx> wrote: > Michael Wookey <michaelwookey <at> gmail.com> writes: >> Of course, I'd love to have git-p4 work seamlessly for this scenario. >> Even Perforce have a KB article on the limitation of the "apple" >> filetype with git-p4: >> >> http://kb.perforce.com/article/1417/git-p4 >> > """ > Step 2: Download Git-p4 > > Recommended version is ermshiperete’s branch, which is available from: > > https://github.com/ermshiperete/git-p4 > > Note: Omit the “git-p4.py25” file, which is an older version that is no longer > needed. > Avoid Kernel.org’s Version of Git-p4 > > Git’s main source at http://git-scm.com/download and > http://www.kernel.org/pub/software/scm/git/ contains an older version of Git-p4 > with limitations that ermshiperete’s branch avoids. > """ > > I can almost guess _who_ wrote this KB ;) > > But this is really frustrating. Why can't people just cooperate to make sure the > version in the main branch is the latest? I tried your suggested version of git-p4 (at rev 630fb678c46c) and unfortunately, the perforce repository fails to import. Firstly, there was a problem with importing UTF-16 encoded files, secondly the "apple" filetype files are still skipped. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html