git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Govind Salinas" <govindsalinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4 question
Date: Fri, 10 Aug 2007 18:25:46 +0200	[thread overview]
Message-ID: <81b0412b0708100925g45b5d3e7j19141374f7f57458@mail.gmail.com> (raw)
In-Reply-To: <69b0c0350708100817u58f74acbyed5c19830cb92ed7@mail.gmail.com>

On 8/10/07, Govind Salinas <govindsalinas@gmail.com> wrote:
> I am having some problems running the script.  It seems that (line
> 1425) $f->{sha1} is uninitialized and causing the import to fail (the
> perforce path is missing the leading "//" I don't know if that is
> intentional).

the line in question deals with local pathnames, so it is expected.
What i don't understand is how did you manage to have the file
without sha1... Could you put a

 print "$tmpfile\n";

after line 1400?
 open($ft,'>',$tmpfile) or die "$tmpfile: $!\n";

and run git-p4-import -v -v -v?
Than it possible to compare lists of the files which is acquired
through p4 change with the list of files output by p4 print.

What perforce client version do you have, BTW?

>  Let me know if you want to continue this off list since
> it isn't really a part of git.

It isn't. We can continue privately

  reply	other threads:[~2007-08-10 16:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  2:53 git-p4 question Govind Salinas
2007-08-10  8:06 ` Alex Riesen
2007-08-10  8:10   ` Alex Riesen
2007-08-10 15:17     ` Govind Salinas
2007-08-10 16:25       ` Alex Riesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-20 16:29 git-p4 Question Fusion Xavier
2015-04-20 16:41 FusionX86
2015-04-20 18:23 ` Sam Vilain
2015-04-21 13:23   ` FusionX86
2015-04-20 19:26 ` Luke Diamand
2015-04-21 13:33   ` FusionX86
2015-04-21 16:53     ` Luke Diamand
2015-04-23 13:42       ` FusionX86
2015-04-24  9:20         ` Luke Diamand
2015-04-24 14:36           ` FusionX86
2015-04-26 22:27             ` Luke Diamand

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=81b0412b0708100925g45b5d3e7j19141374f7f57458@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=govindsalinas@gmail.com \
    /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).