Re: git-p4: problem with commit 97a21ca50ef8

From: Michael Wookey <michaelwookey@gmail.com>
Date: Nov 2, 2011, 22:42 UTC
Message-ID: <CAOk9v+_xaS_Y1m17TROOSjgiscT+QEJWbpZbAZFmh8_tAviF6Q@mail.gmail.com>
In-Reply-To: <loom.20111102T153631-769@post.gmane.org>

On 3 November 2011 01:43, Vitor Antunes <vitor.hda@gmail.com> wrote:

Show 27 quoted lines

> 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.