[prev in list] [next in list] [prev in thread] [next in thread]
List: git
Subject: Re: State of Perforce importing.
From: Simon Hausmann <simon () lst ! de>
Date: 2007-09-19 6:19:11
Message-ID: 200709190819.12188.simon () lst ! de
[Download RAW message or body]
On Wednesday 19 September 2007 01:37:49 David Brown wrote:
> On Mon, Sep 17, 2007 at 12:30:28PM -0700, David Brown wrote:
> > I'd like to track a lot of code living in a Perforce repository, so I've
> > been playing with 'git-p4.py'. Is the one in the contrib/fast-import
> > directory the latest version, or is there a better place.
> >
> > So far, it is having a couple of problems:
> >
> > - The commit comment is empty. It doesn't seem to grab the Perforce
> > description, and the user seems to be <a@b>.
> >
> > - Every revision seems to check every file out of Perforce. This means
> > that for the directory I want, every revision is going to take about
> > 20 minutes.
>
> An additional problem:
>
> - git-p4 doesn't preserve the execute permission bit from Perforce.
Hmm, can you paste the output of
p4 fstat //path/in/depot/to/file/that/is/imported/incorrectly
? I'm interested in the type of the file that p4 reports.
FWIW it works for me ;-)
Thanks,
Simon
["signature.asc" (application/pgp-signature)]
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic