From: Pete Wyckoff <pw@padd•com>
To: Vitor Antunes <vitor.hda@gmail•com>
Cc: Michael Wookey <michaelwookey@gmail•com>,
Git Mailing List <git@vger•kernel.org>,
Luke Diamand <luke@diamand•org>
Subject: Re: git-p4: problem with commit 97a21ca50ef8
Date: Fri, 4 Nov 2011 11:39:57 -0700 [thread overview]
Message-ID: <20111104183957.GB18517@padd.com> (raw)
In-Reply-To: <CAOpHH-W1JO9PLsyp2hQxfr6eyKRr+=pMkaDikV5NcFwF98Miow@mail.gmail.com>
vitor.hda@gmail•com wrote on Thu, 03 Nov 2011 11:04 +0000:
> Hi Michael,
>
> On Wed, Nov 2, 2011 at 10:42 PM, Michael Wookey <michaelwookey@gmail•com> wrote:
> > 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.
>
> I had no intention of directing you to try that version. Sorry for
> misleading you on this.
>
> I just found it interesting that P4's KB contains an article that
> directs users to another version which isn't this one.
We're making contact offline with perforce folk and other git-p4
folk. I'll update with the results.
I've not run the kb version, but for git's git-p4, Utf-16 was
fixed only recently (55aa571). I'm going to revert the apple
filetype issue (97a21ca) that Michael found soon, hopefully
before v1.7.8 goes out.
-- Pete
next prev parent reply other threads:[~2011-11-04 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 23:11 git-p4: problem with commit 97a21ca50ef8 Michael Wookey
2011-11-01 2:08 ` Pete Wyckoff
2011-11-01 4:50 ` Michael Wookey
2011-11-02 14:43 ` Vitor Antunes
2011-11-02 22:42 ` Michael Wookey
2011-11-03 11:04 ` Vitor Antunes
2011-11-04 18:39 ` Pete Wyckoff [this message]
2011-11-05 17:36 ` [PATCH] git-p4: ignore apple filetype Pete Wyckoff
2011-11-07 2:21 ` Michael Wookey
2011-11-07 4:33 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111104183957.GB18517@padd.com \
--to=pw@padd$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=luke@diamand$(echo .)org \
--cc=michaelwookey@gmail$(echo .)com \
--cc=vitor.hda@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox