git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: Git <git@vger.kernel.org>
Subject: Re: State of Perforce importing.
Date: Tue, 18 Sep 2007 16:37:49 -0700	[thread overview]
Message-ID: <20070918233749.GA19533@old.davidb.org> (raw)
In-Reply-To: <20070917193027.GA24282@old.davidb.org>

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.

David

  parent reply	other threads:[~2007-09-18 23:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 19:30 State of Perforce importing David Brown
2007-09-18  6:58 ` Simon Hausmann
2007-09-18  7:27 ` Sam Vilain
2007-09-18 15:49   ` David Brown
2007-09-18 17:53     ` Reece Dunn
2007-09-18 23:19       ` David Brown
2007-09-19  0:20         ` Sam Vilain
2007-09-19  0:26           ` David Brown
2007-09-19  0:23       ` Sam Vilain
2007-09-19 21:20         ` Reece Dunn
2007-09-20  6:12     ` Dmitry Kakurin
2007-09-18 23:37 ` David Brown [this message]
2007-09-19  0:23   ` Sam Vilain
2007-09-19  0:27     ` David Brown
2007-09-19  6:19   ` Simon Hausmann
2007-09-19 17:12     ` David Brown
2007-09-19 18:23       ` Reece Dunn
2007-09-19 18:25         ` David Brown
2007-09-19 18:56           ` Reece Dunn

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=20070918233749.GA19533@old.davidb.org \
    --to=git@davidb.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).